Skip to main content
Glama

Diff two line lists

diff-two-line-lists
Read-onlyIdempotent

Use when you need to compare two lists of lines. Marks each distinct line only_a, only_b or both, matched exactly as sent, as a CSV. $0.01 USDC on Base per answer via x402; a refusal is free.

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": "diff-two-line-lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesTwo lists of lines: a line ---A---, then list A, then a line ---B---, then list B, one item per line. At most 1,048,576 bytes of UTF-8 and 50,000 lines; a line break at the very end is not a line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds genuine value beyond that with the per-answer cost ($0.01 USDC on Base via x402) and the fact that a refusal is free — critical information before an agent spends money. It also discloses exact-match (no normalization) behavior, though it does not say whether output order or duplicate lines are preserved.

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 tight sentences: usage trigger first, then matching semantics and output shape, then payment terms. No filler and nothing a caller needs is buried.

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, read-only computation with no output schema, the description supplies the missing return shape (CSV with only_a/only_b/both labels) and the payment model, which is enough to call it correctly. Minor gap: nothing about output row ordering or how duplicate lines within a list are handled.

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?

Schema coverage is 100% and the schema already documents the ---A---/---B--- delimiter format, byte and line limits, and trailing-newline rule in detail. The description adds only the exact-match interpretation of the input, so the schema is doing the heavy lifting — baseline 3.

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?

States a specific operation (compare two lists of lines), the exact semantics of matching, and the output labeling scheme (only_a, only_b, both, as CSV). None of the siblings (timestamp conversion, base64 decoding, day-count) overlap, so an agent can tell instantly this is the diff tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when you need to compare two lists of lines' gives a clear triggering condition, and 'matched exactly as sent' implicitly excludes fuzzy/normalized comparison. It stops short of explicit when-not guidance or naming an alternative, but no sibling is a plausible substitute here.

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