Skip to main content
Glama

Compare two tables

compare_tables
Read-onlyIdempotent

Compare two versions of a table: with a key column, rows added, removed and changed cell by cell; without a key, rows added and removed.

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_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoColumn that identifies a row, e.g. id (optional).
afterYesTable as an array of flat JSON objects (one per row), up to 500 rows.
beforeYesTable as an array of flat JSON objects (one per row), up to 500 rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the operation read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful behavioral detail beyond annotations by explaining that comparison granularity depends on whether a key is supplied, though it does not describe return ordering or exact output shape.

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?

The definition is a single compact sentence with the main purpose front-loaded and no wasted wording. The colon and semicolon structure cleanly separates the keyed and unkeyed comparison modes.

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 read-only comparison tool with three fully documented parameters and strong annotations, the description provides enough context to select and invoke it correctly. The main remaining gap is exact return structure, but the description does state the categories of differences returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the behavioral consequence of supplying or omitting the key column. It does not add syntax details for before and after, but those are already fully documented in the schema.

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?

The description states a specific verb and resource: compare two versions of a table. It also explains the key-dependent comparison modes, making the tool's purpose clear, though it does not explicitly distinguish itself from sibling tools such as compare_texts or analyze_table.

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 description gives condition-based guidance for the optional key parameter: with a key it performs cell-by-cell change detection, without a key it only reports added and removed rows. It does not state when to choose this tool over alternatives or mention any exclusions, so usage guidance remains implied rather than explicit.

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.