Skip to main content
Glama

document_add_languages

Add target-language sibling versions to a document (grows its language group). Idempotent — languages already in the group are skipped.

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>",
      "target_languages": "<target_languages>"
    },
    "name": "document_add_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYes
target_languagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one important trait, idempotency with already-present languages skipped, but it omits the mutation's side effects (whether new language versions start empty, whether translation runs are triggered), any permission requirements, and what happens to the 20-language cap when the group already has entries.

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, front-loaded with the action and its effect, then the idempotency guarantee. No filler, no repetition of the schema's maxItems limit.

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

Completeness2/5

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

For a two-parameter mutation with no annotations, no output schema and 0% parameter description coverage, the definition leaves too much unspecified: language code format, side effects on the language group, and return behavior are all missing. The idempotency sentence is the only behavioral detail an agent can act on.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and does not. It never explains what document_id refers to (document UUID vs. path) or what form target_languages takes (ISO codes, locale tags, names), leaving the array-of-strings schema ambiguous on the one point that governs success or failure.

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?

The description gives a specific verb and resource: 'Add target-language sibling versions to a document', plus the clarifying parenthetical 'grows its language group', which tells an agent this expands an existing document rather than creating a new one. It does not name any sibling tool, so the boundary with tools like document_update or strings_import is left implicit.

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?

Usage is implied by the phrasing: use this when a document needs additional language versions. The idempotency note tells the agent it is safe to re-run with a superset of languages, which is genuinely useful guidance, but there is no explicit statement of when to prefer this over document_update or strings_import, and no prerequisites are mentioned.

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