Skip to main content
Glama

Get public live track record

get_track_record

Get the public, anonymized live track record: every live Protocol Bank account with its budget, realized PnL and trade count. No auth required — this is public data.

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_track_record"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full disclosure burden, and it does meaningful work: it states the data is public and anonymized, that no auth is required, and it names the three returned fields, which compensates for the missing output schema. It stops short of disclosing response size, freshness/latency, or whether the full account set is ever truncated.

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 sentences, zero waste, and the core payload description is front-loaded ahead of the auth note. The em-dash clause carries the access constraint economically rather than in a separate paragraph.

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 zero-parameter, read-only retrieval with no annotations and no output schema, the description covers the essentials: what comes back, the granularity (every live account), and access requirements. Missing only secondary detail such as refresh cadence or result-volume behavior, which an agent could use to decide whether to call it speculatively.

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?

The tool takes zero parameters and the schema is an empty object at 100% coverage, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies, with no parameter-level gaps to penalize.

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 uses a specific verb and resource ("Get the public, anonymized live track record") and enumerates the payload (budget, realized PnL, trade count). It implicitly distinguishes itself from account-scoped siblings by stressing "every live Protocol Bank account" and "public," though it never names an alternative. The intent is unambiguous.

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 only implied: the agent can infer this is the aggregate, public-facing listing rather than a personal or single-account query. There is no explicit when-to-use framing, no mention of when to prefer get_trading_overview, get_activity, or get_positions, and no stated exclusions. Adequate but leaves the routing decision to inference.

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