Skip to main content
Glama

AgentNative: Public Data, Government Datasets, Federal Statistics & Official Records

Query an imported official dataset

query_imported_dataset
Read-onlyIdempotent

Free preview returns up to 25 rows with $skip to 475 and a next_url page cursor; use sample_imported_dataset first, then page free results. Paid auth raises the bounds to 100 rows and $skip 5000 at 120 requests per minute, and unlocks the exact-match filter. Returns normalized rows, freshness, and provenance.

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": {
      "dataset_id": "<dataset_id>"
    },
    "name": "query_imported_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
dataset_idYes
filter_fieldNo
filter_valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, and the description adds substantial context beyond them: free-tier caps (25 rows, $skip 475), paid-tier caps (100 rows, $skip 5000), a 120 req/min rate limit, an auth requirement that unlocks a filter, and the shape of the returned payload. This is exactly the kind of operational detail annotations cannot express.

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?

Two tight sentences with the free-preview limits and pagination cursor front-loaded, then paid escalation and return shape. It is dense but every clause carries operational information; the semicolon-chained clauses are the only mild readability cost.

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?

No output schema exists, so the description's mention of normalized rows, freshness, and provenance is necessary and sufficient at a high level. For a 5-parameter query tool with tiered limits and pagination, the behavioral picture is nearly complete, lacking only error/empty-result behavior.

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 burden, and it largely does: it maps top and skip to concrete free vs paid bounds that the schema's static maximums do not reveal, and identifies filter_field/filter_value as the exact-match filter gated behind paid auth. dataset_id goes unexplained and the field/value pairing of the filter is only implied.

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?

States a specific verb (query) and resource (imported official dataset) and immediately characterizes the result as "normalized rows, freshness, and provenance." It also distinguishes itself from sample_imported_dataset by positioning that tool as the precursor step, though it does not contrast with aggregate_imported_dataset.

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 ordering rule ("use sample_imported_dataset first, then page free results") and explains the tier gating that selects paid behavior, including which capability (exact-match filter) is unavailable free. It omits guidance on when to prefer aggregation or the materialization siblings, but the primary when-to-use path is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources