Skip to main content
Glama
Sign In
pathiel

pathiel

by Julian-dev28
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_status

Read-only

Check the install's status to see trading mode, equity with open positions, registered accounts, and network. It also shows whether trading is enabled or read-only and the builder fee.

Instructions

Start here. Get the install's status: the trading mode, equity with open positions in brief, and the registered accounts with the one that trades; on a public install also the network (mainnet or testnet), whether trading is enabled (an API wallet key is configured) or read-only, and the builder fee. Use first in a session and whenever an order is refused as read-only. For full balances and liquidation risk use get_account; for settings use get_config. Read-only. With no wallet connected it still answers, showing trading as read-only; a venue that cannot be reached shows in the equity fields. Returns {status: {mode, equity, equity_by_dex, positions, install (public installs): {network, trading, builder_fee}}, accounts: {count, accounts[], bot_trades_with}}.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial context beyond that, notably that it succeeds with no wallet connected and reports read-only, and that an unreachable venue surfaces inside the equity fields rather than failing. It also outlines the response payload, which is needed since no output schema exists.

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?

Front-loaded with 'Start here' and packed with decision-relevant detail, but the single dense paragraph is long and mildly redundant in restating read-only after already describing the read-only trading state. The embedded return-type sketch is compact and earns its words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, no-output-schema status tool, the description covers the returned fields, the degraded no-wallet and unreachable-venue cases, and the read-only safety profile. An agent has everything needed to call it and interpret the result without opening anything else.

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 the baseline is 4; there are no parameter semantics to clarify and the empty object schema is complete on its own. No additional parameter guidance is possible or needed.

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

Purpose5/5

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

Specific verb-and-resource opening ('Get the install's status') followed by an explicit enumeration of what is returned: trading mode, equity with open positions, registered accounts, and on public installs network/trading/builder fee. It is clearly distinguishable from get_account and get_config, which are named as adjacent tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit timing guidance ('Start here', 'Use first in a session', 'whenever an order is refused as read-only') and routes to alternatives with conditions: get_account for full balances and liquidation risk, get_config for settings. Both when-to-use and when-to-use-something-else are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools