Skip to main content
Glama
mukul8896

trading-mcp-server

by mukul8896

switch_to_live_mode

Activates live trading mode to enable real order execution, pending manual enabling of ALLOW_LIVE_TRADING flag.

Instructions

Set TRADING_MODE=live. NOTE: real orders remain impossible until a human also sets ALLOW_LIVE_TRADING=true in .env.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses a critical behavioral trait: that setting live mode does not enable real orders; a human must set ALLOW_LIVE_TRADING. This is sufficient for a simple parameterless tool.

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?

The description is extremely concise, with two sentences that front-load the action and then provide the essential caveat. Every sentence is necessary and informative.

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?

Given no parameters, no output schema, and no annotations, the description covers the core action and the critical limitation. It is complete enough for the tool's simplicity, though it could mention related tools for clarity.

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?

No parameters exist, and schema coverage is 100%. The description adds no param info since none is needed, meeting the baseline for this dimension.

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 explicitly states that it sets TRADING_MODE=live, which is a clear action on a specific resource. It distinguishes itself from sibling tools by noting the additional requirement for live trading, aligning with the sibling switch_to_paper_mode.

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?

The description provides clear context: the tool switches to live mode but real orders remain impossible without human intervention. This guides the agent on when this tool alone is insufficient, though it does not explicitly compare with alternatives like switch_to_paper_mode.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mukul8896/trading-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server