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

trading-mcp-server

by mukul8896
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

execute_delivery_buy_after_validation

Execute a prepared delivery buy order after human approval. Guarantees that only validated buy orders are placed, with no sell execution.

Instructions

Execute a prepared DELIVERY BUY live order. Only call after the human has explicitly approved. Delivery SELL can never be executed through this system.

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

Input Schema

NameRequiredDescriptionDefault
approval_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided. Description does not disclose side effects, safety profile, or failure modes. Only mentions approval requirement but lacks details on what 'prepared' means or behavior on invalid tokens.

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?

Three sentences, each essential: purpose, condition, and constraint. No redundant or verbose language. Front-loaded with key information.

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

Completeness2/5

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

Given critical nature of live order execution, missing details like return value, error handling, and token explanation. No output schema or annotations. Incomplete for an agent to use safely.

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

Parameters1/5

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

The single parameter 'approval_token' has no description in schema (0% coverage) and description does not explain its purpose, format, or how to obtain it. No added meaning beyond schema.

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 action: 'Execute a prepared DELIVERY BUY live order.' It specifies the order type (buy, not sell) and distinguishes it from sibling tools like execute_intraday_order_after_validation.

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?

Explicitly states when to use: 'Only call after the human has explicitly approved.' Also warns against misuse: 'Delivery SELL can never be executed through this system.' Does not name alternatives but context implies other tools for sell or intraday orders.

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