Skip to main content
Glama
dataparity

dataparity

dataparity_list_diff_runs

List recent saved table-diff runs, newest first, so you can find a prior comparison and then retrieve its full report by run ID.

Instructions

List recent saved diff runs, newest first. Successful dataparity_diff_tables calls are saved locally; use dataparity_get_diff_run to retrieve a full report.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dataparity_list_diff_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of runs to return (1-100, default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: runs are those persisted locally from successful dataparity_diff_tables calls, and this tool returns summaries rather than full reports. It omits storage lifecycle details (retention, whether deletes remove entries, what happens if no runs exist) which matters for a no-annotation read tool.

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 with no filler. Ordering and origin are front-loaded, and the alternative-tool pointer comes last as an actionable next step.

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 simple one-parameter list tool with no output schema, the description supplies enough: what is listed, in what order, where the entries originate, and where to go for detail. It could be slightly stronger by indicating the shape of a summary entry, since there is no output schema to fall back on.

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% with a single well-documented `limit` parameter (range and default 20). The description adds no additional meaning about the parameter, 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?

States a specific verb and resource ('List recent saved diff runs') plus an ordering guarantee ('newest first'). It implicitly separates itself from dataparity_get_diff_run, which it names as the full-report path, so an agent can distinguish the summary-list role from the single-run retrieval role.

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?

Gives clear routing guidance: use dataparity_get_diff_run when a full report is needed, implying this tool is for discovery/summary only. It does not state explicit exclusions (e.g., when not to list, or how it relates to dataparity_delete_diff_run), so it falls short of the top band.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.