Skip to main content
Glama

get_dataset

Retrieve a survey dataset's validation report, summary, and design details using its dataset ID.

Instructions

A dataset: validation report, summary, design.

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

Input Schema

NameRequiredDescriptionDefault
dataset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it supplies none. It does not say whether this is a read-only lookup, what happens on an unknown dataset_id, whether access is scoped, or what the shape of the response is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but short because it is under-specified rather than because it is efficient. The fragment has no front-loaded statement of purpose and reads like an excerpt of field names rather than a definition.

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 simple single-parameter read tool, which lowers the bar, but with no annotations and no output schema the description must at least say what is returned. Listing candidate contents (validation report, summary, design) is not enough to let an agent invoke it confidently or interpret the result.

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% for the single required dataset_id parameter, so the schema offers nothing beyond the title. The description does not explain what a dataset id is, how to obtain one, or its format, leaving the parameter's meaning to be guessed from the name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text "A dataset: validation report, summary, design" is a noun fragment that lists content but never states an action verb. The retrieval semantics are only inferable from the tool name get_dataset and the single dataset_id argument, not from the description itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many siblings (get_project, get_result, list_projects). An agent gets no help deciding when this tool applies versus those.

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