Skip to main content
Glama

List Compare API - what is only in A, only in B, in both

list_compare
Read-onlyIdempotent

Compare two lists (one item per line): items only in A, only in B and in both, with counts. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/list-compare.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listA": "apple\nbanana\ncherry",
      "listB": "banana\ncherry\ndate"
    },
    "name": "list_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
listAYesList A, one item per line
listBYesList B, one item per line
caseSensitiveNoCapital letters count as different

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint), and the description adds information they cannot convey: server-side execution, immediate file deletion, no persistence, a 25 calls/day per-IP quota, and a $0.001-per-call paid path with its endpoint. Quota and data-retention disclosure are exactly the behavioral facts an agent needs before deciding to call.

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?

Purpose and output shape come first, followed by privacy, then pricing, so the ordering is sensible and front-loaded. The pricing/URL sentence is the weakest element but still carries operational value for quota-aware agents.

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

Completeness5/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 must state what comes back, and it does ('only in A, only in B and in both, with counts'). Combined with annotations, full schema coverage, and the retention/rate-limit notes, an agent has everything needed to call it correctly.

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%, so listA/listB/caseSensitive are all documented in-schema, and the description's 'one item per line' merely restates the existing parameter descriptions. It says nothing extra about the semantics of caseSensitive or how duplicates or blank lines are treated, so baseline 3 applies.

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?

The description names a specific verb and resource ('Compare two lists') and enumerates the exact output breakdown: items only in A, only in B, and in both, with counts. That is enough for an agent to identify the tool's job without opening the schema, and no sibling in the catalog overlaps with list diffing.

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?

It gives a concrete input-format rule ('one item per line') and a concrete availability rule (25 free calls/day, then paid x402), which tells the agent when the tool is callable. There is no explicit when-not-to-use or named alternative, but the purpose is narrow enough that no plausible alternative exists.

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