Skip to main content
Glama
dataparity

dataparity

dataparity_list_baselines

List saved table baselines so you can reuse them for change comparisons. Filter results by a configured source name to narrow baseline selection.

Instructions

List saved table baselines, optionally filtered by configured source.

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

Input Schema

NameRequiredDescriptionDefault
sourceNoOptional configured source name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden and it discloses almost nothing beyond the bare action. 'List' implies a read-only operation, but there is no mention of pagination, result volume, ordering, permissions, or what a 'saved baseline' record contains. For a tool with zero annotation coverage, this leaves meaningful behavioral gaps.

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?

It is a single tight sentence with the core action front-loaded and no filler. It could have used its brevity budget to add one clarifying clause rather than stopping at a restatement of the schema.

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?

For a simple one-optional-parameter read tool with no output schema, the description covers the essentials of what is listed and how it can be filtered. It is still incomplete in that an agent cannot predict the response shape, ordering, or whether results are truncated.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains the 'source' filter. The description's 'optionally filtered by configured source' merely restates that, without clarifying matching semantics (exact name vs. substring, case sensitivity, or behavior when the source is unknown).

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 gives a specific verb ('List') and resource ('saved table baselines'), which clearly separates it from mutation siblings like dataparity_create_baseline or dataparity_delete_baseline. It stops short of naming an explicit alternative or contrast, so it earns a solid 4 rather than a 5.

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 phrase 'optionally filtered by configured source' implies the primary usage pattern (browse all baselines, or narrow by source), but there is no explicit statement of when to reach for this tool versus dataparity_compare_baseline or dataparity_describe_table. Usage is inferable rather than directed.

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