Skip to main content
Glama

Dataset details

dataset_info
Read-onlyIdempotent

Call this with a slug from list_datasets to learn what a dataset holds before reading it: readme (source, method, caveats), record schema (fields, types, required, allowExtra), the latest versions with their record counts, top contributors and an AI summary when there is one. It holds no records: read_dataset reads a page of them. Free, no key; an unknown slug, or a private project without your operator's key, answers not found. With an agent key: query_dataset for counts and filters, dataset_manifest for a whole version's files, dataset_diff for what changed between versions, and contribute_records to add records, which must match the schema.

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": {
      "slug": "<slug>"
    },
    "name": "dataset_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesthe dataset project's slug, as list_datasets gives it (e.g. agent-api-observatory): 3–60 lowercase letters, digits and dashes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"the dataset project's slug, as list_datasets gives it (e.g. agent-api-observatory): 3–60 lowercase letters, digits and dashes"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real value beyond them: no records are returned, the call is free and keyless, and an unknown slug or a private project without an operator key returns not found. Auth and failure semantics are the useful additions here; only rate limits or response sizing are left unstated, which is minor for a metadata read.

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?

Front-loaded with the action and its input, then the return contents, then sibling routing — a logical order with no filler sentences. It is dense and long-ish for one parameter, but each clause carries distinct information (contents, no-records caveat, auth, alternatives) rather than repeating the title.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so by enumerating the payload sections. Combined with auth behavior and explicit handoffs to the read/query/manifest/diff/contribute siblings, nothing an agent needs in order to call this correctly is missing.

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?

With one parameter at 100% schema coverage, the schema already carries format and pattern detail. The description still adds sourcing guidance the schema does not — the slug comes from list_datasets — which is the one piece of semantic context an agent needs to construct a valid call.

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

Purpose5/5

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

States a specific verb and resource ('call this with a slug ... to learn what a dataset holds') and then enumerates exactly what comes back: readme, record schema, latest versions with counts, contributors, AI summary. It explicitly distinguishes itself from the sibling that returns data ('It holds no records: read_dataset reads a page of them'), so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

Gives a clear when-to-use ('before reading it') plus explicit routing to five alternatives by condition: query_dataset for counts/filters, dataset_manifest for a version's files, dataset_diff for changes, contribute_records for writes, read_dataset for records. When-not conditions are also covered via the not-found behavior for unknown or private slugs.

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.