Skip to main content
Glama

Fox River Press

Get a dataset

get_dataset
Read-onlyIdempotent

One dataset in full: its rows, columns, sources, method, version history and how to cite it. Use list_datasets for the 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": {
      "id": "<id>"
    },
    "name": "get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA dataset id from list_datasets, for example credit-deadlines

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. Above that bar the description adds genuine value by disclosing the breadth of the returned record, letting an agent anticipate a large payload covering data, provenance, versioning and citation in one call.

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?

Two short sentences with zero filler; the payload contents are listed first and the prerequisite second, so the reader gets the important information immediately.

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?

With no output schema, the description correctly carries the burden of describing return contents and does so thoroughly, while annotations handle safety and idempotency and the lone parameter is fully documented. Missing only minor operational detail such as payload size behavior or error handling for invalid ids.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter already documents itself with an example id (credit-deadlines). The description only reinforces provenance ("from list_datasets"), which duplicates the schema rather than adding syntax, format, or failure semantics such as what happens with an unknown id.

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?

"One dataset in full" plus an enumeration of exactly what comes back (rows, columns, sources, method, version history, citation) makes the resource and its payload unambiguous, and it separates itself from list_datasets. The only weakness is that the retrieval verb is implied by a noun phrase rather than stated, and "rows" leaves it slightly unclear whether raw row data or a schema summary is returned.

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?

It explicitly routes the agent: use list_datasets to obtain the ids needed here, which is the real prerequisite for this tool. It stops short of when-not-to-use guidance (e.g. when list_datasets output alone suffices, or when to prefer a sibling like compare_chargers), but the context it does give is actionable.

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