deactivate-document-linkDeactivate (disable) a recipient link by its token. Reversible via "activate-document-link".
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | The token of the link to deactivate. | |
| doc_id | Yes | The public id of the document the link belongs to. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds valuable context that the action is reversible via another tool, aligning with annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words, efficiently conveying the tool's purpose and key behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple deactivate action, the description is sufficient. It doesn't explain return values, but with no output schema, this is acceptable given the tool's simplicity and the context provided by annotations and schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both parameters. The description adds no additional meaning beyond the schema, meeting the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (deactivate/disable) on a specific resource (recipient link) identified by token, and distinguishes it from the sibling 'activate-document-link' by noting reversibility.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions when to use it (to deactivate a link) and implies an alternative (activate-document-link for reactivation). However, it doesn't clarify when to use deactivate vs. delete-document-link, leaving ambiguity for permanent removal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation (document management, PDF manipulation, automation, analytics, etc.) with clear boundaries, making it easy for an agent to select the correct one.
All tool names follow a strict lowercase-with-hyphens pattern and use consistent verb-noun phrasing (e.g., 'create-document', 'list-documents', 'add-pdf-security'), ensuring predictability.
At 45 tools, the server far exceeds the recommended 3-15 range for a well-scoped set. While the coverage is comprehensive, the high number may overwhelm agents and suggests insufficient consolidation.
The tool surface covers the full lifecycle of documents and PDFs—creation, retrieval, update, deletion, archiving, security, OCR, splitting, merging, automation, analytics, and more—with no obvious gaps.