Skip to main content
Glama

check_document

Validates a draft against a facts file, flagging number inaccuracies, context issues, blocked phrases, and tone warnings with line-level findings and supporting fact traces.

Instructions

Check a draft (Markdown or plain text, at most 200,000 characters) against the facts file.

Returns passed, error and warning counts, findings with line/column and message, and a trace from each accepted number to the fact that supports it. A longer document is rejected with an error instead of being checked in part.

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": {
      "text": "<text>"
    },
    "name": "check_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does a decent job: it discloses the size limit, the all-or-nothing rejection behavior (no partial checking), and the shape of the response, including a trace linking accepted numbers to supporting facts. It does not say whether the call is purely read-only or whether the facts file must be pre-populated, which prevents 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 short sentences, front-loaded with the core action, followed by return shape and the size constraint. No redundant restatement of the name and no filler.

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 one-parameter validation tool with an output schema, the description covers purpose, input format, hard limits, and response shape, so an agent can call it correctly. The remaining gap is operational context such as prerequisites on the facts file and whether any state is modified.

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 0% and the single parameter is bare ('text'), so the description does the work: it identifies the parameter's content as a draft in Markdown or plain text and gives a concrete 200,000-character ceiling. Only the exact unit/measurement details and any encoding constraints are left unstated.

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?

Specific verb ('Check') plus a specific resource pair ('a draft ... against the facts file'), with the accepted input formats named inline. It is unmistakably distinct from the only sibling, list_facts, without needing to name it.

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 (use it when you have a draft to verify against the facts file) and the description supplies a hard precondition: documents over 200,000 characters are rejected rather than partially checked. It never states when not to use it or points to any alternative workflow.

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

Deploy Server

Other Tools