Skip to main content
Glama

Control the AI trading agent

control_trading_agent

Control the AI trading agent. Actions: "pause" (stop opening new trades, keep managing positions), "resume" (start scanning again), "stop" (emergency stop — halt everything), "approve"/"reject" (resolve a pending trade in manual approval mode), "set_approval" (+ mode: auto|manual — choose whether entries need your approval). Requires authentication.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "control_trading_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoRequired for set_approval: "auto" places entries automatically, "manual" holds each entry for approval.
actionYesThe control action: pause/resume/stop the agent, approve/reject a pending trade (manual approval mode), or set_approval to switch entry mode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the authentication requirement, the distinction between pause (keeps managing positions) and stop (halts everything), and that approve/reject only apply in manual approval mode. Gaps remain — it doesn't say whether stop is reversible, what happens to open positions on stop, or what a call returns.

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?

Purpose is front-loaded in the first clause, followed by a tight enumerable action list where each action gets exactly one explanatory clause. No filler sentences and no repetition of the schema's enum list.

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 two-parameter control tool with no output schema and no annotations, the definition covers the essential action vocabulary and the auth requirement. It is slightly incomplete on outcome expectations — there is no indication of what a successful call returns or what error surfaces when approve is called with no pending trade.

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?

Schema coverage is 100% and both enums are documented, so the baseline is 3. The description adds genuine meaning on top of the schema by explaining the behavioral consequence of each action value and noting that mode is paired with set_approval ('+ mode: auto|manual — choose whether entries need your approval'), which tells the agent when the optional parameter is required.

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?

The description names a specific verb+resource ('Control the AI trading agent') and immediately enumerates all six actions with one-line semantics for each. This makes it clearly distinguishable from read-only siblings like get_trading_overview or get_positions, which cannot change agent state.

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

Usage Guidelines4/5

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

Per-action conditions are stated (pause = stop opening new trades, stop = emergency halt, approve/reject = manual approval mode only, set_approval = switch entry mode). This gives clear context for choosing each action. It does not explicitly exclude or point to sibling tools (e.g., for inspecting positions before pausing), so it stops short of a 5.

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