Skip to main content
Glama
Data.gov Semantic MCP

Data.gov Semantic MCP

by trevorspecht

Compare Public Indicators

compare_public_indicators
Read-only

Compares county-level population and unemployment indicators from verified Databricks snapshots, returning summary counts, filtered rows, coverage gaps, units, and evidence IDs for reproducible analysis.

Instructions

Compare registered population and unemployment indicators in Databricks.

Runs only reviewed parameterized SQL for a verified snapshot; returns summary counts over all compared counties (quote these for any "how many counties" claim), filtered rows, missing coverage, units and evidence ID. Population change is percent; rate change is percentage points. Refuses unsupported or unconfigured requests. Use get_analysis_evidence to reproduce the result and cite source versions.

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

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint by disclosing that only reviewed parameterized SQL runs against a verified snapshot, that summary counts cover ALL compared counties while rows are filtered, and that units differ (percent vs percentage points). The refusal behavior and the 'quote these for any how-many-counties claim' caveat are exactly the kind of behavioral context annotations cannot convey.

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?

Five short sentences, front-loaded with purpose and immediately followed by behavioral caveats; every sentence carries information. Slight density (the parenthetical quoting instruction) makes it a touch busy but nothing is filler.

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?

An output schema exists, so return-shape explanation is unnecessary and the description's coverage of refusal logic, units, and evidence ID is adequate on the behavior side. However, for a nested, fully undocumented request object, the definition leaves an agent unable to construct a correct call without reading the raw schema.

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% and the single required 'request' object hides ten nested properties (metric_ids, start_year/end_year, state_fips, county_fips, limit, sort_by, both direction filters). The description explains only the unit semantics of the change values and says nothing about the 24-county cap, the two-metric requirement, or FIPS scoping, so it fails to compensate for the coverage gap.

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 ('Compare') and two named resources ('registered population and unemployment indicators'), plus the execution context ('in Databricks'). It also routes the agent to get_analysis_evidence for reproduction, so it is distinguishable from siblings without opening a 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?

Usage context is clear: use it to compare population and unemployment indicators over counties, and follow up with get_analysis_evidence to reproduce and cite. It also states an exclusion ('Refuses unsupported or unconfigured requests'), but never explains when to prefer assess_comparison or find_data_for_question instead.

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