Skip to main content
Glama

Get AI trading overview

get_trading_overview

Get the AI trading cockpit state: agent status (running/paused/stopped), total equity, trading wallet, max loss, today/all-time PnL, open positions and the latest activity. Without a configured wallet this reads the guest demo account (paper mode).

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

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 exist, so the description must carry the behavioral burden, and it does disclose a meaningful non-obvious trait: without a configured wallet it reads the guest demo account in paper mode. The 'Get'/'reads' phrasing makes the read-only nature clear, and the field list implies a single-call snapshot. It does not state permission requirements, whether data is live or cached, or rate limits, which keeps it below a 5.

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, front-loaded with the core action and resource, followed by the enumerated state and then the wallet caveat. The field list is dense but each item is genuinely part of the returned snapshot, so every clause earns its place.

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?

With no output schema, the description must explain what comes back, and it enumerates the returned fields well enough for an agent to decide whether this call supplies the data it needs. The guest-demo fallback covers the main edge case. Minor gaps remain: no mention of snapshot freshness or response shape.

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, so there is nothing for the description to clarify beyond what the schema shows. The baseline for a parameterless tool applies, and nothing in the description misleads about inputs.

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 ('Get') with a named resource ('AI trading cockpit state') and then enumerates exactly what that state contains: agent status, equity, wallet, max loss, PnL, open positions, latest activity. An agent can tell it is an aggregate snapshot rather than a granular query. It does not explicitly differentiate from siblings like get_positions or get_activity, which cover subsets of this data, so it stops short of a 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?

Usage is implied by the word 'overview': call this for a consolidated dashboard view, and the sibling list suggests granular tools exist for individual pieces. However, there is no explicit statement of when to prefer this over get_positions/get_balance/get_activity, and no exclusions or prerequisites beyond the wallet note. The wallet fallback caveat is the only conditional guidance given.

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