Skip to main content
Glama

Remove Document From Project

disassociate_document
DestructiveIdempotent

Remove a document you own from a Project you own, addressed by slug — does not delete the document itself. Requires the projects:write scope in addition to documents. Identify the Project with exactly one of project_id (uuid) or project_key — passing both, or neither, is an error. Repeating the same call is a no-op.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "disassociate_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug of a document you own
project_idNoProject id — exactly one of project_id or project_key is required
project_keyNoAdopted Project key — exactly one of project_id or project_key is required

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is partly covered. The description still adds real value beyond them: the auth scope requirement, the crucial fact that the document itself survives, and the exactly-one-identifier error condition. It stops short of saying whether re-association later is supported or what the response looks like, which keeps it from a 5.

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

Conciseness5/5

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

Three sentences, all front-loaded: the operation and its non-destructive scope come first, then auth, then the identifier constraint and idempotency. No filler, no restatement of the title, and every clause carries information an agent needs.

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

Completeness4/5

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

For a 3-parameter tool with rich annotations and no output schema, this covers the essentials: what it does, what it does not destroy, what auth it needs, how to identify the project, and that repeats are no-ops. The only gap is the return/error surface beyond the both-or-neither case, which is a minor omission given the safety hints already present.

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 coverage is 100%, so the baseline is 3 and the schema already documents all three parameters. The description still adds a cross-parameter rule not obvious from any single field — that passing both or neither identifier is an error — and reinforces the ownership requirement on `slug`. Genuine but modest value on top of an already complete 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 (Remove), a specific resource relationship (document from a Project), and the addressing key (slug), then explicitly rules out the most confusable interpretation with 'does not delete the document itself' — which cleanly separates it from the delete_document sibling. An agent can identify the operation and its scope without opening the schema.

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

Usage Guidelines4/5

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

Gives clear preconditions (ownership of both document and project, `projects:write` in addition to `documents`) and an invocation constraint (exactly one of project_id or project_key). The boundary against delete_document is implied strongly by 'does not delete the document itself', but the inverse sibling associate_document is never named as the way to re-add, so routing guidance stops just short of explicit alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.