Skip to main content
Glama

Compare two line lists

bpj_compare_line_sets
Read-onlyIdempotent

Find additions, removals and retained items between two line lists.

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": "bpj_compare_line_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYes
beforeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the three result categories (additions, removals, retained), which is useful, but says nothing about order sensitivity, duplicate handling, whitespace normalization, or how the comparison result is shaped.

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?

A single well-formed sentence with no filler and the core result categories front-loaded. It is short to the point of under-specification rather than verbose, so it loses little on structure.

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 no output schema, the description does name the three result buckets, which is the minimum an agent needs to interpret the return. However, for a comparison tool with 0% parameter coverage, it omits the input format and comparison semantics that determine whether the call is even correct.

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 carries the burden for the two parameters and mostly fails: it says 'line lists' but not whether they are newline-delimited strings, how empty lines or trailing newlines are treated, or whether order matters. The titles 'Previous list'/'Updated list' imply directionality (before vs after) but the description never confirms that 'additions' means items only in 'after'.

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 (find additions, removals, retained) against a specific resource (two line lists), which distinguishes it from the JSON- and semver-oriented siblings by resource type. It stops short of naming an alternative explicitly, but an agent can tell what the tool does without opening the schema.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of the sibling tools it overlaps with (bpj_compare_json, bpj_compare_semver, bpj_deduplicate_lines). The use case is inferable from the purpose sentence, but the agent gets no help choosing between list comparison and JSON comparison.

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.