Skip to main content
Glama

decisions

Read-onlyIdempotent

Your trading agent's record at Cubicle: every decision newest first (paged) with its trace id, practice order, fill and the hash that chains it; decisions by action, fills, realised test dollars, open practice positions, whether the ledger's chain is whole, and the reader gate's word on your answers. PRACTICE: test dollars, never proof.

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

Input Schema

NameRequiredDescriptionDefault
limitNodecisions per page (default 50, max 200)
offsetNoskip this many of the newest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuine context: the practice-only, simulated-dollar nature of the records ('test dollars, never proof'), newest-first paging, and a chain/hash integrity notion plus what sounds like an authorization gate on answers. However, it doesn't clarify the practical consequence of a broken chain or what the 'reader gate' does and returns, so the added transparency is suggestive rather than actionable.

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

Conciseness2/5

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

One dense, semicolon-chained run-on sentence mixes the tool's purpose with a long inventory of response fields and an environment disclaimer. Key framing (what the tool returns) is buried rather than front-loaded, and much of the field jargon doesn't earn its place without context.

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?

For a simple two-parameter read tool with annotations and no output schema, the description conveys enough to call it (paged, newest first, read-only, practice data), but the enumerated response elements are too vague to predict the actual return and the 'reader gate' concept is left unexplained. Adequate but with clear gaps given no output schema to fall back on.

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%, so both limit and offset are already documented. The description's 'newest first (paged)' reinforces offset ordering, but it adds no format or boundary detail beyond the schema's own 'default 50, max 200' and 'skip the newest'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause 'every decision newest first (paged)' gives a recognizable verb-resource-scope, but the rest of the description piles in unrelated-sounding payloads (actions, fills, test dollars, positions, chain integrity, reader gate) so it is unclear whether this is a decision list or a general ledger/status dump. It never contrasts itself with the sibling 'decide' or other read tools, leaving the agent to guess.

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?

No statement of when to call this rather than a sibling tool such as 'decide' or 'account'. The only guidance-ish content is the 'PRACTICE: test dollars, never proof' caveat, which describes the environment, not when to use the 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