Skip to main content
Glama

reconciliation_report

Read-onlyIdempotent

Generates a data quality reconciliation report showing records that could not be settled, links to review, and how many links each rule created.

Instructions

Data quality: records reconciliation could not settle, links to review, and how many links each rule made.

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": "reconciliation_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered and the description owes nothing there. What the description does not add is any behavioral context beyond the content list — no indication of result volume, truncation, whether all rules are reported or only failing ones, or whether the report reflects a live or cached state. The output schema covers return values, so the remaining gap is modest but real.

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?

A single front-loaded sentence prefixed with the domain ('Data quality:') and no filler — appropriate for a zero-argument report. The terseness borders on elliptical ('records reconciliation could not settle'), which costs a little clarity but not space.

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?

The description plus the full annotation set and the output schema cover a zero-parameter tool: the agent knows it is a safe, idempotent read whose return shape is defined elsewhere. What is described — unresolved records, review links, per-rule link counts — is enough to decide whether to call it, though the missing usage guidance is scored separately under that dimension.

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?

The tool takes zero parameters, so there is no schema semantics for the description to compensate for. Baseline 4 applies; nothing about argument meaning is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the report's contents — records reconciliation could not settle, links to review, and per-rule link counts — so an agent can infer this is a reconciliation data-quality report. However, it is a verbless noun phrase and makes no attempt to distinguish itself from siblings like compliance_findings or root_cause_candidates, which are also diagnostic reports.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative or complementary tool. The agent must guess whether this is the right diagnostic entry point versus the other findings-style siblings.

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