Skip to main content
Glama

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

Buy one warehouse page

purchase_dataset_page_once

Pay USD 0.01 for one eligible page using a compatible Tempo wallet.

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

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
dataset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the cost (USD 0.01) and a wallet prerequisite ('compatible Tempo wallet'), which is real value. But for a paid mutation it omits idempotency/retry-charging behavior, what 'eligible' means, whether repeat purchases of the same page re-charge, and what the response contains.

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 with no filler; the price and wallet constraint lead. It is efficient but so terse that it leaves obvious questions unanswered, which is arguably under-specification rather than ideal conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a monetary, mutating operation with no annotations, no output schema, and undocumented parameters, so the description should do heavy lifting. It conveys price and wallet requirement but not paging semantics, eligibility rules, or error/charge outcomes, leaving key gaps.

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 three parameters (dataset_id, skip, top), so the description must compensate and largely doesn't. 'One eligible page' weakly implies paging, but it never maps skip/top to page offsets or limits, nor clarifies the dataset_id identifier format.

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?

The description gives a specific verb and resource: 'Pay USD 0.01 for one eligible page.' That is a concrete purchase action scoped to a single page, and it names the payment mechanism (Tempo wallet). It does not distinguish itself from siblings such as recover_dataset_page or sample_imported_dataset, so it falls short of a 5.

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 guidance on when to use this versus alternatives. The 'once'/'one page' framing hints at single-page semantics, but the description never says when a page is eligible, when to call recover_dataset_page instead, or what to do after buying one page.

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