Tools, resources, and prompts

The MCP capabilities available to assistants connected to Fusial, with their required permission scopes.

Your client discovers tool names, descriptions, and input schemas from the server. The list below describes the full catalog; your connection sees only tools allowed by its primary scopes. Call fusial_whoami to check your access. Some arguments need additional scopes, as described below.

Account

Tool	Purpose	Scope
`fusial_whoami`	Identify the workspace and effective permission scopes.	Any authenticated connection

Contracts and clause search

Tool	Purpose	Scope
`fusial_list_contracts`	Filter the portfolio by status, type, owner, counterparty, or template; search titles and counterparty names.	`contracts:read`
`fusial_get_contract`	Read metadata, owner, dates, value, and optional related information.	`contracts:read`
`fusial_get_contract_analysis`	Read the latest AI summary, extracted terms, and section outline.	`contracts:read`
`fusial_search_contract_text`	Search clauses by meaning and keywords across the workspace or within a contract.	`search:read`
`fusial_read_contract_sections`	Read clause text by ordinal, heading keyword, or section ID.	`contracts:read`
`fusial_get_contract_activity`	Read a contract's audit timeline, newest first.	`contracts:read`
`fusial_list_contract_versions`	List document versions and their sources.	`contracts:read`
`fusial_get_version_download_link`	Get a short-lived signed URL for a document version.	`contracts:read`

Including obligations in fusial_get_contract requires obligations:read; including signature requests requires signatures:read. Download links return a URL, not the file's binary contents.

Semantic search uses query embeddings and is subject to Fusial's AI usage limits. Search excerpts may be shortened; use fusial_read_contract_sections to inspect the relevant wording and cite its section ordinal.

Portfolio and workspace reads

Tool	Purpose	Scope
`fusial_list_obligations`	Find deadlines across contracts; defaults to outstanding obligations, soonest first.	`obligations:read`
`fusial_list_signature_requests`	Find signature requests and see who is still expected to sign.	`signatures:read`
`fusial_get_signature_request`	Read signatories, signing timestamps, audit events, and the signed document reference.	`signatures:read`
`fusial_list_counterparties`	Find organizations by name or relationship type.	`counterparties:read`
`fusial_get_counterparty`	Read a profile, notes, contacts, and optionally its contracts.	`counterparties:read`
`fusial_list_templates`	Find templates available for generating contracts.	`templates:read`
`fusial_get_template`	Read intake variables, required values, and optional document blocks.	`templates:read`
`fusial_get_analytics_report`	Run overview, cycle-time, throughput, redline-acceptance, SLA, distribution, or signature reports.	`analytics:read`
`fusial_list_workspace_members`	Resolve people to user IDs and check who can own contracts.	`members:read`

fusial_get_counterparty includes contracts by default, which also requires contracts:read. Pass includeContracts: false to read just the profile without that scope.

Changes and draft generation

Tool	Purpose	Primary scope
`fusial_create_contract`	Create a contract record with metadata and an owner; no document is attached.	`contracts:write`
`fusial_update_contract`	Update metadata, value, counterparty, or date anchors.	`contracts:write`
`fusial_set_contract_status`	Make an allowed lifecycle transition.	`contracts:write`
`fusial_set_contract_owner`	Assign an eligible workspace member as owner.	`contracts:write`
`fusial_create_contract_from_template`	Fill a template and generate a draft document and contract record.	`contracts:write`
`fusial_create_counterparty`	Create an organization; duplicate names are refused by default.	`counterparties:write`
`fusial_update_counterparty`	Update a name, domain, notes, or relationship tags.	`counterparties:write`
`fusial_resolve_obligation`	Complete, dismiss, or reopen an obligation.	`obligations:write`
`fusial_set_contract_anchors`	Update effective or execution dates, term, and renewal settings, recalculating deadlines.	`contracts:write`

Additional requirements and behavior:

Changing date anchors through fusial_update_contract or fusial_set_contract_anchors also requires obligations:write, because it recalculates the contract's obligation deadlines.
Generating a draft requires templates:read. Supplying counterpartyName without counterpartyId also requires counterparties:write, because the operation may create that counterparty.
Before generating a document, read the template's requiredKeys and collect missing values. Generation produces a draft and does not send it.
Contract creation does not check for duplicates. Search before creating a record. Counterparty creation can use ifExists: "return_existing" to reuse an existing name.
Status changes must follow the contract's allowedNextStatuses and cannot move it to OUT_FOR_SIGNATURE. Send signature requests in Fusial.

Resources

Resources provide document context in clients that support them. Replace the IDs in these URI templates with IDs returned by the tools.

URI	Content	Primary scope
`fusial://playbook`	Workspace negotiation positions.	`contracts:read`
`fusial://contract/{contractId}`	Contract brief with metadata and available related information.	`contracts:read`
`fusial://contract/{contractId}/analysis`	AI summary, key terms, and outline as JSON.	`contracts:read`
`fusial://contract/{contractId}/text`	Up to 25 sections of the latest version, capped at 400,000 characters.	`contracts:read`
`fusial://counterparty/{counterpartyId}`	Counterparty profile and available portfolio information.	`counterparties:read`
`fusial://template/{templateId}`	Template variables and optional blocks as JSON.	`templates:read`

The contract brief includes obligations and signatures only when the connection has their corresponding read scopes. For large documents, use section reads to inspect specific clauses instead of relying on the text resource as a complete copy.

Reusable prompts

Clients with MCP prompt support can offer these workflows as commands or picker entries. The server filters them by their declared scopes; individual tool calls within a workflow may need additional scopes for related records.

Prompt	Inputs	Workflow
`review_contract_risk`	Required `contractId`; optional `focus`.	Compare clauses with the playbook and cite findings.
`summarize_contract`	Required `contractId`; optional `audience` (`exec`, `legal`, or `sales`).	Adapt a contract summary to its reader.
`renewal_watchlist`	Optional `horizonDays` (defaults to 90) and `counterpartyId`.	List renewals and notice deadlines with action dates.
`draft_counterparty_response`	Required `contractId` and `issue`; optional `posture`.	Draft replacement wording and a cover note for a human to send.
`new_contract_from_template`	Optional `templateId` and `counterparty`.	Choose a template, collect intake values, and generate a draft.

You can also ask for these workflows in plain language when your client does not expose a prompt picker.