Skip to main content
Glama

Compare two texts

compare_texts
Read-onlyIdempotent

Line-by-line unified diff between two texts, with counts of added and removed lines and a similarity ratio.

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": {
      "before": "<before>",
      "after": "<after>"
    },
    "name": "compare_texts"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYesNew text.
beforeYesOriginal text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value by describing the diff format and the summary metrics returned, which annotations cannot convey. It does not mention limits on input size or diff truncation, keeping it short of 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?

A single sentence that front-loads the operation and then the outputs, with no filler words. Every clause earns its place and nothing is repeated from the 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 two-parameter, stateless utility with no output schema, the description supplies enough: what is computed, what is returned in summary form, and how safety behaves via annotations. Only edge behavior (large inputs, truncation, exact ratio definition) is left unstated, which is acceptable at this complexity.

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?

With 100% schema description coverage and only two clearly named parameters (before, after), the schema carries the semantics. The description reinforces that the operation is between two texts but adds no format, encoding, or size details beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 (line-by-line unified diff between two texts) and previews the outputs (added/removed counts, similarity ratio). It does not explicitly distinguish itself from the nearest sibling, compare_tables, but that gap is minor for a text-specific utility.

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?

Guidance is implied by the name and phrasing: use it when you need a diff between two strings. There is no explicit when-to-use or when-not-to-use statement, and no pointer to compare_tables for tabular data, so the agent must infer the boundary.

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.