Skip to main content
Glama
Data.gov Semantic MCP

Data.gov Semantic MCP

by trevorspecht

Inspect Dataset

inspect_dataset
Read-only

Retrieve bounded dataset metadata, distributions, terms, and source dates by harvest-record UUID to verify a Data.gov search result without fetching distribution URLs.

Instructions

Inspect a search result's harvest-record UUID, not its publisher identifier.

Returns bounded metadata, distributions, distribution terms and source dates. Uses the transformed payload when present, otherwise labels the raw JSON. Does not follow distribution URLs. Missing rights never authorize data fetching.

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": {
      "harvest_record_id": "<harvest_record_id>"
    },
    "name": "inspect_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
harvest_record_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, but the description adds real behavioral context beyond them: output is bounded, transformed payloads are preferred with raw JSON labeled otherwise, distribution URLs are never followed, and missing rights are not an authorization to fetch data. The only gap is that 'bounded metadata' quantifies nothing (no cap or pagination behavior).

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?

Four short sentences with no filler, front-loaded with the identifier disambiguation, then output shape, then behavioral limits. Every sentence carries a distinct constraint an agent would otherwise get wrong.

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?

For a single-parameter read-only tool with an output schema available, the description covers identity, scope, transformation provenance, and a rights/fetching guardrail. Nothing an agent needs to call it correctly appears to be missing.

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?

Schema coverage is 0%, so the description must carry the parameter meaning, and it does by specifying that the single argument is a harvest-record UUID rather than a publisher identifier. The 36-character length bound in the schema corroborates the UUID format, but the description does not state where in a search result to find the field.

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 (inspect) and resource (dataset) and immediately pins down the identifier type: a search result's harvest-record UUID, not its publisher identifier. That distinction is the main ambiguity for this tool and it is resolved in the first sentence.

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?

Usage context is implied by 'a search result's harvest-record UUID', which tells the agent the ID must come from a prior search, and 'Does not follow distribution URLs' delimits scope. However, there is no explicit when-to-use-this-vs-another statement, and none of the siblings (e.g. get_analysis_evidence, find_data_for_question) are referenced.

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