Skip to main content
Glama
Data.gov Semantic MCP

Data.gov Semantic MCP

by trevorspecht

Assess Comparison

assess_comparison
Read-only

Check whether registered indicators support a county comparison by validating metrics, geography, periods, and snapshot readiness; return reasons when unsupported.

Instructions

Check whether registered indicators support a descriptive county comparison.

Checks metrics, geography, periods and snapshot readiness; returns reasons when unsupported. Population is July 1; unemployment is annual average. A comparison cannot establish causation. Consult data.gov://capabilities for supported IDs.

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": {
      "request": "<request>"
    },
    "name": "assess_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the description is free to add real context: it discloses that unsupported cases return reasons, notes data caveats (population as of July 1, unemployment as annual average), and warns that the comparison cannot establish causation. It also points to data.gov://capabilities for valid IDs. It doesn't state response shape or failure behavior beyond 'reasons', but the added caveats are substantive.

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?

The core check sentence is front-loaded and the caveats are delivered as short declarative fragments with no filler. The causation disclaimer is arguably boilerplate but is short enough to justify itself as a scope statement.

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?

An output schema exists, so not explaining return structure is acceptable, and the description covers what is validated, that failures yield reasons, data vintage caveats, and where to find supported IDs. The remaining gap is guidance on the input constraints (metric count, sort/filter options) needed to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0% across a nested request object with roughly ten properties, so the description carries the full explanatory burden. It only obliquely maps to three of them ('metrics, geography, periods' → metric_ids, state_fips/county_fips, start_year/end_year), while limit, sort_by, population_direction, and unemployment_direction are undocumented anywhere. The maximum of two metric_ids and the FIPS format/length constraints are likewise unexplained.

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?

Uses a specific verb and resource: 'Check whether registered indicators support a descriptive county comparison', and enumerates the four dimensions checked (metrics, geography, periods, snapshot readiness). It's clearly a pre-flight validation rather than the comparison itself, though it never names the sibling tool (compare_public_indicators) that performs the actual comparison, so that distinction is inferred rather than stated.

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?

Implies the tool should be called before running a county comparison, and 'returns reasons when unsupported' signals its gatekeeping role. However, there is no explicit when-to-use/when-not-to-use guidance, no statement that it must precede compare_public_indicators, and no mention of what to do when the check fails.

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