Skip to main content
Glama

SizeMyFile

Compare text files

text_compare
Idempotent

See line differences between two files. Bounded processing; 32 MiB combined input per operation, at most 50 files. Queues a run and returns its ID for progress and output tracking. Uses cloud allowance.

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": {
      "artifacts": "<artifacts>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "text_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
artifactsYes
idempotency_keyYes
allow_server_fallbackNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, idempotent, closed-world behavior, and the description goes further by disclosing the 32 MiB combined input bound, the 50-file ceiling, that the call queues a run and returns an ID, and that it consumes a cloud allowance. That is real cost, limit, and asynchrony disclosure beyond the annotations. What remains unstated is whether the run is cancellable or what happens when limits are exceeded.

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

Conciseness4/5

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

Four short, front-loaded sentences with the core action first, then limits, then execution model. The style is telegraphic (fragments like 'Uses cloud allowance.') but no sentence is filler; the cost note could have been folded into the limits sentence for tighter flow.

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

Completeness3/5

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

With an output schema present, not describing return values is acceptable, and the async run-ID lifecycle is covered. However, for a tool with an undocumented nested `options` object, a 0% parameter coverage and an unexplained server-fallback switch, the description leaves too much for the agent to guess about invocation semantics.

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% across 4 parameters, including a nested empty `options` object, so the description must compensate and largely does not. Only the 50-file cap loosely maps to `artifacts` maxItems; `idempotency_key` and `allow_server_fallback` are never explained, and the description's 'two files' framing actively conflicts with an artifacts array accepting 1-50 items.

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: 'See line differences between two files,' which tells an agent exactly what the tool produces. It does not differentiate from plausible siblings like data_compare, document_text, or model_compare, so an agent must still infer which comparison tool fits.

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 'between two files' implies the use case, but there is no explicit when-to-use or when-not guidance and no naming of alternatives such as data_compare. Usage must be inferred from the resource type alone.

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.