Skip to main content
Glama

Get Model Records

get_model_records
Read-onlyIdempotent

Read dated simulated model records. Missing values remain unavailable; simulated records are not actual trades. List results keep chart_spec and history as HTML link objects. chart_url (chart link) links each row to its chart page; limit caps rows. No embedded chart data. Reads service records; does not generate research or consume allowance.

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

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD
fromNoYYYY-MM-DD
limitNo
modelNo
cursorNo
statusNo
tickerNo
languageNoen or zh-Hant

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false and openWorldHint=false, so the bar is lower. The description still adds real context: records are simulated and not actual trades, missing values stay unavailable, chart_spec/history come back as HTML link objects rather than chart data, and no allowance is consumed. That is disclosure an agent could not infer from annotations alone.

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?

Purpose is front-loaded and the remaining sentences carry caveats about data origin and return shape. Minor waste appears in redundant asides such as 'chart_url (chart link)' and 'No embedded chart data,' which partly restate the previous sentence, but overall it is compact.

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?

With no output schema, the description does useful work describing row-level return shape (chart_url link, HTML link objects for chart_spec/history). However, gaps remain around pagination via cursor, the meaning of status values, date-range semantics for from/to, and the model codes, which matter for a freely callable tool with eight optional filters.

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 only 38%, so the description needs to compensate and largely does not. It explains that 'limit caps rows' but says nothing about from/to, cursor pagination, the status enum values (open/closed/end_unavailable/restated), the model enum codes, ticker, or language. One of eight parameters is covered.

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?

Opens with a specific verb-plus-resource: 'Read dated simulated model records.' An agent can tell this is a read of backtest/model output rows rather than a research request. It stops short of explicitly distinguishing itself from a close sibling such as query_public_records, so it lands at 4 rather than 5.

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?

The final clause 'does not generate research or consume allowance' implies a read-only, non-billed path, which is useful routing context, but usage is only implied. There is no explicit when-to-use or when-not-to-use statement naming an alternative 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