Skip to main content
Glama

append_document

Agrega contenido (markdown) al FINAL de un documento, sin reenviar lo que ya tiene. Devuelve el resumen del documento resultante.

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": {
      "document_id": "<document_id>",
      "content": "<content>"
    },
    "name": "append_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesLo que se agrega, en markdown
document_idYesID del documento
base_versionNoupdated_at con el que se leyó el documento
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation profile is known. The description usefully confirms that existing content is preserved and that a `resumen` is returned, but says nothing about base_version conflict behavior or what happens if the document does not exist — the main risk area for an append.

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?

Two short sentences with zero waste: the append-at-end behavior is front-loaded, followed immediately by the return value. Nothing is repeated from the name or title.

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 four-parameter mutation with full schema coverage and no output schema, the description covers the core behavior and even names the returned `resumen`. It falls short only on concurrency/versioning semantics implied by base_version, which an agent would want spelled out.

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

Parameters3/5

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

Schema coverage is 100%, so all four parameters including base_version and workspace_id are already documented in the schema. The description only restates that content is markdown appended at the end, adding no new syntax or format guidance beyond the structured fields; baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Agrega contenido ... al FINAL de un documento') and adds the defining constraint that existing content is not resent, which separates it from a full-document update. It does not name a sibling such as patch_document or update_document, so the differentiation is implied rather than explicit.

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

Usage Guidelines3/5

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

The phrase 'sin reenviar lo que ya tiene' implies this is the tool to pick when adding at the end rather than rewriting, but no explicit when-to-use, when-not-to-use, or alternative tool is named. An agent must infer the boundary with patch_document/update_document.

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.

Resources