Skip to main content
Glama

Get dataset

get_dataset
Read-onlyIdempotent

Inspect an authorized dataset's current schema, statistics and immutable version history. Version history is paged; unavailable history does not invalidate the returned dataset metadata.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 20,
      "dataset_id": "returned-dataset_id"
    },
    "name": "get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
dataset_idYes

Output Schema

NameRequiredDescriptionDefault
datasetYes
relatedYes
warningsYes
context_completeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior beyond that: version history is returned in pages, and unavailable history does not cause the whole response to fail. That partial-result semantic is the kind of detail an agent cannot get from structured fields.

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 sentences, front-loaded with the core purpose, and each sentence carries distinct information with no filler. The second sentence is slightly dense and 'unavailable history' is a touch opaque, which keeps it short of a perfect score.

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

Completeness3/5

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

An output schema exists, so return-value detail is not the description's job, and the partial-failure note covers the main non-obvious behavior. The gap is parameter-level: with three undocumented parameters at 0% schema coverage, an agent still lacks guidance on paging controls and defaults.

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%, so the description carries the burden for three parameters. It only hints at paging via 'Version history is paged', without connecting that to the limit/offset parameters, stating their defaults, bounds, or whether paging applies to anything other than history. dataset_id is implied but never explained as the identifier of the dataset to inspect.

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 uses a specific verb (Inspect) with a named resource (an authorized dataset) and enumerates what is returned: current schema, statistics, and immutable version history. That distinguishes it from mutation siblings such as run_model_fit or upload_text_asset, though it does not explicitly separate it from read siblings like describe_table or get_asset.

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 is implied by the phrase 'authorized dataset', which signals a precondition on access. However, there is no explicit statement of when to choose this tool over alternatives such as describe_table or search_catalog, and no when-not guidance. An agent must infer the selection context.

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