Skip to main content
Glama
Sign In
trading-mcp-server

trading-mcp-server

by mukul8896
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

execute_intraday_order_after_validation

Executes a pre-validated intraday order after receiving explicit human approval via an approval token.

Instructions

Execute a prepared INTRADAY live order. Only call after the human has explicitly approved the prepared order shown to them.

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": {
      "approval_token": "<approval_token>"
    },
    "name": "execute_intraday_order_after_validation"
  }
}

Input Schema

NameRequiredDescriptionDefault
approval_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided; the description conveys that the tool executes a live order (destructive), but does not disclose error handling, token validity effects, or other operational details.

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 a single sentence with 18 words, front-loading the action and necessary condition. No extraneous information.

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

Completeness3/5

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

Given no output schema and one parameter, the description explains the action and prerequisite but omits return values, success indicators, or potential errors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter 'approval_token' lacks description in the schema or description; the description implies its origin but does not explain its format or how to obtain it.

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 clearly states the verb 'execute' and the resource 'prepared INTRADAY live order', distinguishing it from sibling 'execute_delivery_buy_after_validation' and other validation tools.

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 specifies a prerequisite ('only call after human explicitly approved'), but does not mention alternatives or when not to use this tool relative to siblings like 'validate_order_before_execution'.

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