Skip to main content
Glama

Dataset Detail

dataset_detail
Read-onlyIdempotent

One dataset entry from the product catalog. (Source: BankRegReports.)

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": {
      "key": "<key>"
    },
    "name": "dataset_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesDataset key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds nothing behavioral beyond a provenance note ('Source: BankRegReports') — no statement about what an unknown key does, whether the lookup is case-sensitive, or what shape the entry takes.

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

Conciseness3/5

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

At two short sentences there is no padding, and the resource statement is front-loaded. However, the parenthetical source attribution is marginal value for an agent and the brevity comes at the cost of substance rather than from efficiency.

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?

With no output schema, the description is the only place an agent could learn what a 'dataset entry' contains (fields, metadata, counts), and it says nothing. For a single-parameter read tool this is under-specified even accounting for annotation coverage.

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% for the single 'key' parameter with an example ('bank'), so the schema carries the parameter burden. The description adds no meaning about key format, valid values, or lookup behavior, which is the expected baseline-3 outcome when the schema is fully documented.

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 description 'One dataset entry from the product catalog' is essentially a restatement of the name and title 'Dataset Detail' with no verb and no indication of what a dataset entry contains or what the tool returns. It hints at singular retrieval versus the sibling dataset_catalog, but the distinction is left implicit rather than stated, leaving an agent to infer the operation.

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 when-to-use guidance, no mention of when not to use it, and no reference to the obvious sibling dataset_catalog for browsing versus fetching a single entry. The agent must guess the selection criteria between this and the catalog tool.

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