Lightbringer

Name: Lightbringer
Author: lightbringer

Capture, analyze, validate, and submit inventions, and collaborate on patent reviews.

От сообществаРаботаетБез входаГлобальныйБесплатноТолько чтение

Что умеет

Какие данные видит

Нужен ли аккаунт

Не нужен: сервер работает без входа

Capture, analyze, validate, and submit inventions, and collaborate on patent reviews.

Список инструментов сервера (20)

Технические названия из tools/list. Нужны только разработчикам.

whoami	Returns the signed-in Lightbringer user and organisation for this connection.
list_innovations	Lists the innovations in the user's Lightbringer organisation, each with a title, reference number, and web link. Accepts an optional free-text query to filter results.
get_innovation	Returns an innovation record rendered as markdown, including the problem, solution, technical details, and prior art.
update_innovation	Updates one or more sections of an existing innovation record with new content and returns the updated innovation. Overwrites the specified sections.
request_patent_preparation	Requests Lightbringer patent preparation for an already registered innovation, expressing the user’s decision to pursue patent filing. Advances the innovation description into the Lightbringer team’s workflow and triggers email notifications to the assigned specialist and inventor. Returns whether preparation was newly requested or had already been requested. Email delivery status is not included. Separate from registration; does not itself complete preparation, file a patent or pay for services.
get_innovation_template	Returns the current innovation registration template: the schema, per-field guidance, and structure used to create a new innovation, together with capture guidance on gathering the innovation content — interviewing an inventor who is present, or authoring from existing material — before drafting.
register_innovation	Registers a new innovation in the user's Lightbringer organisation from a structured payload matching the current registration template. Validates before creating anything: invalid input returns field-specific errors without registering a record; success returns the saved identifier, reference number, web link, and any non-blocking warnings. Meant for capturing a concept that is not already recorded; enrichment of an existing innovation belongs in update_innovation. Completes registration without requesting patent preparation or filing. Requires a payload matching the current registration schema.
search	Searches the Lightbringer organisation's documents (inventions, patent applications, and reports). Returns matching results, each with an ID, title, and summary. A document result also lists its parts: the texts it has accumulated across its lifecycle (innovation description, priority draft, application text revisions), each with an ID that fetch accepts. Supports cursor-based pagination. Document content is indexed asynchronously, so a recently created or edited document can take a short while to become searchable; an empty result reflects the current index and does not by itself establish that a matching document is absent.
fetch	Returns the full content of a single document — invention, patent application, strategy, or report — identified by its ID. A document has several texts across its lifecycle; a bare document ID returns the most advanced one (the newest application text, else the priority draft, else the innovation description), and the response lists every part with its own ID, such as document:<id>#priority_draft or document:<id>#application_text:<revisionId>. Pass a part ID to read that text instead.
list_tasks	Lists the current user’s unexpired automated tasks in the connected organisation, optionally for an innovation. Recovers task IDs after a lost response or conversation. Returns recorded status summaries without polling upstream analyses. Tasks and findings expire 30 days after creation. Pagination can return an empty page with a continuation cursor. Professional service requests are separate.
delete_task	Permanently deletes an automated task owned by the current user in the connected organisation, including its cached findings. Available in any execution state. Deletion removes tracking; it does not cancel upstream analysis, delete the innovation, or withdraw a professional service request. Repeated deletion returns not_found.
start_innovation_feedback	Starts automated analysis of a registered innovation description across clarity, problem framing, completeness, or all focus areas. Returns one task_id, status, progress, available findings and per-analysis errors. Findings contain readable title/description fields; findings_error means findings are unavailable, not absent. Queued or running tasks continue through get_task_status with the same task_id. Succeeded, partially_succeeded and failed are terminal. Ending the wait does not cancel analysis. Separate from novelty assessment, patent search, FTO, attorney review and patent preparation requests.
get_task_status	Returns an automated feedback task by task_id, with the same status, progress, findings and per-analysis errors as start_innovation_feedback. Refreshes active analyses and saves their status and available findings in Lightbringer. Succeeded, partially_succeeded and failed are terminal; queued and running tasks are still in progress. findings_error denotes unavailable findings and does not change terminal execution status. This endpoint does not track professional service requests, patent preparation or filing milestones.
send_developer_feedback	Sends a report about the Lightbringer tools themselves to the engineering team: broken or surprising tool behaviour, missing capabilities, or friction encountered while working. Reports are sent to a human-reviewed engineering Slack channel, together with user, organisation, and connected-client identifiers and organisation name when available, and are not visible to the signed-in user. A good report stays high-level — the goal, the approach, the obstacle — and leaves out document text, invention details, and other confidential material.
list_reviews	Lists reviews where the user is a participant or creator, including each review's status, the user's response status, which participants are still awaited, the title and reference number of the report or case under review, and, for report reviews, the invention the report is connected to.
get_review	Returns a review: its metadata, the document under review rendered as markdown, each comment thread with a stable comment ID, and the review discussion feed (standalone comments on the review itself). Attorney redlines are included as suggested changes, each with the original text, the proposed replacement, and an optional rationale. Proposed amendments embedded in the document (agent-drafted changes to a block) are listed in artifact.amendments and in a trailing text block: each carries the baseline text, the proposed text, a redline with <del>/<ins> tags, and a unified patch; the document body itself shows the baseline at the amended block. The document is artifact.markdown in the structured result and is also returned as its own text block. When it cannot be rendered through this API, a short notice takes its place and artifact.status / artifact.reason say so.
respond_to_review	Records the user's decision on a review — approve or request changes — sends review-response email notifications, and returns the updated review state. Meant for after the user has explicitly chosen their response. An approval cannot be withdrawn through this tool; a request for changes can later be upgraded to approval.
add_comment	Adds a comment to the document under review, anchored to a quoted passage of the review markdown, and returns the created comment. If the quoted passage is ambiguous or cannot be located, the response indicates this along with candidate passages. A comment anchored within an existing thread is added as a reply. Targeted users with document access receive email and in-app mention notifications.
add_discussion_comment	Posts a standalone comment to the review's discussion feed, visible to the review creator and all participants, and returns the updated discussion. Unlike add_comment, it is not anchored to a passage of the document — it suits general remarks, questions, or status updates about the review as a whole. Eligible review participants receive in-app and email notifications.
reply_to_comment	Adds a reply to an existing comment thread identified by its comment ID, and returns the created reply. Targeted users with document access receive email and in-app mention notifications.