Skip to main content
Glama

document_create

Create a document from inline text/markdown/html and fan out target languages.

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

Input Schema

NameRequiredDescriptionDefault
titleNo
contentYes
project_idNo
content_typeNo
glossary_idsNo
source_languageNo
target_languageNo
target_languagesNo
styleguide_version_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for a 9-parameter mutation, yet it discloses almost nothing behavioral. "Fan out target languages" is the most consequential claim and it is left undefined: it is unclear whether this launches translation runs, is synchronous or asynchronous, consumes quota, or how glossary/styleguide settings affect the outcome — all of which matter given the run_start/run_estimate siblings.

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

Conciseness3/5

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

A single front-loaded sentence with no filler, so it is not bloated. However, the brevity comes at the cost of substance: one clause is spent on formats while several equally important parameters and the fan-out mechanics go unmentioned.

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 nine-parameter creation tool with no annotations and no output schema, the definition is far too thin. It omits what is returned (document id, triggered runs), how fan-out behaves, and how glossary/styleguide/project context affect creation, so an agent cannot call it with confidence beyond the required content field.

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 for nine parameters and it does so only for content formats and target languages. It says nothing about project_id, title, glossary_ids, styleguide_version_ids, source_language, or the distinction between target_language and target_languages (singleton vs. up to 20 fan-out).

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 states a specific verb (create) and resource (document), plus the accepted source formats (text/markdown/html) and the language fan-out behavior. It implicitly separates it from document_add_languages, which handles languages on an existing document, but it never names that sibling.

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?

"From inline text" implies this is the path when content is supplied directly rather than imported from a file, so the when-to-use is inferable. There are no explicit exclusions, prerequisites, or named alternatives such as strings_import or document_add_languages, leaving the agent to infer the routing.

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