Skip to main content
Glama

Microverse Market Data

List available history

list_history
Read-onlyIdempotent

Dates with recorded order-book history, per venue (crypto exchanges, about the last 30 days). With a venue, also lists the symbols recorded on its most recent day.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description only needed to add context. It does: the ~30-day retention window and the mode-dependent behavior (passing a venue also returns symbols from the most recent day) are non-obvious traits an agent could not get from annotations. Return shape and pagination are not described.

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

Conciseness5/5

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

Two tight sentences with no filler. The primary output (dates) is front-loaded, and the conditional venue behavior follows immediately.

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

Completeness4/5

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

For a one-parameter, non-destructive discovery tool with no output schema, the description covers scope, time window, and both call modes. What remains unspecified is the concrete return format (e.g., whether dates are strings or objects), which is a minor gap at this complexity.

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?

Schema coverage is 0%, so the description must carry the single parameter, and it does: 'venue' selects the venue scope, and supplying it changes the result to include symbols from that venue's most recent day rather than just dates. The contrast between the no-arg and with-arg behavior is spelled out; only value format/examples are missing.

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 states a specific resource (dates with recorded order-book history) and its scope (per venue, crypto exchanges, ~30 days), which separates it from siblings like list_symbols and get_historical_book. It is clear enough without needing the schema, though it never explicitly names what it is not.

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 rather than stated: an agent can infer this is a discovery tool for finding available dates/symbols before calling get_historical_book. There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named.

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