Skip to main content
Glama
dataparity

dataparity

dataparity_list_tables

List table names in a configured source, optionally filtered by schema, to identify candidate tables for comparison or schema inspection.

Instructions

List table names in a configured source. Use this to find candidate tables, then call dataparity_describe_table when you need column names, types, or nullability before choosing diff keys.

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": {
      "source": "<source>"
    },
    "name": "dataparity_list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaNoOptional schema to restrict the listing to.
sourceYesThe configured source name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return content (table names only, not columns), but says nothing about pagination, result limits, error behavior for an unknown source, or permissions.

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 sentences, zero waste: the purpose leads, and the follow-on routing advice is packed into the second sentence. Nothing is repeated or padded.

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 two-parameter read tool with no output schema, the description covers purpose, return content, and the natural next step. It stops short of explaining how to obtain valid source names or how large listings behave, which keeps it from being fully complete.

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 description coverage is 100%, so both parameters are already documented in the schema, and the description does not add syntax or format beyond that. Baseline 3 applies; the description's only extra signal is the implicit requirement that source be a configured name.

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 table names in a configured source") and immediately contrasts with the sibling dataparity_describe_table, which returns column detail. An agent can tell the two apart without opening either schema.

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 an explicit usage pattern: call this first to find candidate tables, then call dataparity_describe_table when column names, types, or nullability are needed before choosing diff keys. It lacks any note about discovering valid source names (e.g., via dataparity_list_sources) required by the mandatory source parameter.

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