Skip to main content
Glama

fynk MCP

by com.fynk.app
OverviewDiscussionsAdmin

Move document to signing stage

move-document-to-signing-stage
Destructive

Moves a document to the signing stage and invites signatories to sign.

Use this tool when:

  • The document's current stage is one of: draft, approved_draft, review, approved_review

  • You want to start the signing process

This stage transition may be blocked by checkpoints on the document, or by unresolved preconditions (missing signature blocks, unresolved proposals, mandatory dynamic fields without values, active editor sessions or working copies, etc.). A refusal here reports just the first problem it runs into; call get-document-info first and read workflow_state.stage_transitions.signing.blockers to see everything that is in the way at once.

If the document has a signature_type set, the signature_type argument - if provided - must match it; otherwise the document's signature_type will be used. If the document has no signature_type, the one provided here (or the account default) will be used.

A qes or aes_eid signature_type requires sequential_signing=true. aes_eid is only available when the account has enabled AES (eID) in its settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNoCustom message included in the signatory invitation email. If not sent, falls back to the document's external_signatory_invitation_message.
document_uuidYesUUID of the document to move to signing. If you don't already have the document's UUID, use the list-documents tool to find it.
signature_typeNoSignature security level to use. If not sent, either the document's assigned signature_type or the account default will be used.
sequential_signingNoIf true, signatories sign in the order defined by their signing_order. Cannot be false when signature_type is qes or aes_eid. If not sent, the document's current setting is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to open the document in fynk
nameNoName of the document
uuidNoUnique identifier for the document. Do not show to the user unless they ask for it
stageNoWhat stage the document is in currently
_entity_typeNoOnly relevant for tooling. Do not show to the user
document_typeNoIf present, indicates what kind of document this is. Absent when the document has no type assigned
workflow_stateNoGives an indication of which stage transitions, etc are possible to perform on this document. This object is technical state, not display content: when relaying it to the user, always render it as natural-language prose and never echo raw field names or snake_case values (e.g. say 'signing cannot be started yet because not every signature block has been assigned to a signatory' instead of mentioning 'can_start_signing' or 'signature_block_signatory').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only say destructiveHint=true and openWorldHint=true; the description goes well beyond by disclosing the signatory-invitation side effect, the checkpoint/precondition blockers that can refuse the move, and the fact that a refusal reports only the first problem while get-document-info surfaces all of them. That is exactly the kind of behavioral context an agent needs before invoking a mutating, irreversible action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action, then a scannable bulleted when-to-use block, then blocker and parameter logic. It is dense and slightly long, but every sentence (blockers, refusal behavior, precedence, sequential_signing constraint) carries actionable information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-step, blockage-prone mutation, the description covers preconditions, failure behavior, the diagnostic alternative, and cross-parameter constraints. An output schema exists, so return values need not be described, and nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description adds real meaning beyond it: the precedence rule that a provided signature_type must match the document's existing one, and the requirement that qes/aes_eid force sequential_signing=true with aes_eid gated on account settings. The message and document_uuid semantics are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Moves') + resource ('a document') + target stage ('signing stage') and the immediate side effect ('invites signatories to sign'). This clearly separates it from move-document-to-review-stage and move-document-to-done-stage without needing to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'Use this tool when' block with the exact set of valid current stages (draft, approved_draft, review, approved_review) plus the intent condition. It also routes the agent to the alternative get-document-info when a transition is blocked, so both when-to-use and a diagnostic fallback are spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All fynk MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources