Skip to main content
Glama

OpticAlpha Data

get_dataset

Read-only

Fetch one public OpticAlpha dataset by slug (see list_datasets). Returns JSON with stats, tables, as_of timestamp, license and citation, or Markdown if format is markdown.

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

Input Schema

NameRequiredDescriptionDefault
slugYesDataset slug
formatNoDefaults to json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds useful content beyond that: the returned payload fields (stats, tables, as_of, license, citation) and the alternate Markdown rendering, which no annotation communicates.

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?

A single front-loaded sentence naming the action, the required identifier, the sibling cross-reference, and the return shape. Dense but every clause earns its place; the parenthetical and trailing clause make it slightly packed.

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?

With no output schema and only two enum-typed parameters, the description supplies exactly what is missing: the shape of the returned document and the format switch. Nothing an agent needs to invoke it correctly is absent.

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 coverage is 100% and both parameters are enum-constrained with descriptions, so the schema does the heavy lifting. The description only restates the slug keying and the markdown alternative, adding no format syntax or default behavior beyond what the schema shows.

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 ('Fetch one public OpticAlpha dataset by slug') and explicitly names the sibling list_datasets as the enumeration counterpart, so the agent can distinguish this single-item retrieval from listing.

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?

'Fetch one ... dataset by slug (see list_datasets)' gives clear context for use and routes the agent to the sibling when it lacks a slug. It stops short of stating exclusions, such as what happens with a non-public or invalid slug.

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