Skip to main content
Glama

Cash

get_account
Read-only

The cash the user tracks in each market (hk, us, cn), in that market's currency, as the website's asset header shows it. amount is null where cash is not tracked. Recording a trade moves the cash of a market where it is tracked.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
cashNo
errorNo
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: amounts are per-market in local currency and null where cash is not tracked, which tells an agent how to interpret missing values, and it notes the data is affected by trade recording.

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?

Three short sentences, front-loaded with what the tool returns, then the null convention, then a behavioral note. The final sentence about recording trades is slightly convoluted in phrasing but earns its place by explaining that balances are derived rather than static.

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?

An output schema exists, so return values need not be described, and the description covers the market scope, currency semantics, and null handling — everything an agent needs to call and interpret a zero-parameter read. The only marginal gap is that the market list is presented as fixed without saying whether it can vary per user.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 would apply — but the description does add the meaningful detail that the three markets each report in their own currency, which shapes interpretation of the (schema-documented) output rather than the empty input. Nothing about inputs needs explaining.

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 names a concrete resource — the user's tracked cash per market (hk, us, cn), denominated in each market's currency — and anchors it to the website's asset header, so an agent knows exactly what this returns. It is clearly distinct from sibling tools like get_trades or get_dividends, though it never explicitly contrasts itself with them.

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: it is evidently the read tool for cash balances, and the note that recording a trade moves cash hints at when the data changes. There is no explicit 'use this when you need account balances' statement and no named alternative for related queries.

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.