Skip to main content
Glama
Sign In
trademind-unified-mcp

trademind-unified-mcp

by vishalkumar-2006
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_execution_details

Retrieve a detailed execution breakdown for a trade by supplying its trade ID, with optional workflow identifier for deeper analysis.

Instructions

Get detailed execution breakdown for a specific trade ID

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": {
      "trade_id": "<trade_id>"
    },
    "name": "get_execution_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
trade_idYes
workflow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must convey behavior. It only states 'Get detailed execution breakdown' without mentioning read-only nature, potential latency, or any side effects. Lacks necessary transparency.

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?

Single sentence is concise and front-loaded. However, the brevity sacrifices necessary detail for clarity.

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 no output schema and no annotations, the description is too minimal. It does not explain what the breakdown includes, how to interpret results, or any prerequisites.

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?

Schema coverage is 0%, so description must explain parameters. It only mentions 'trade ID' but does not clarify trade_id or the optional workflow_id parameter. No added value over the schema.

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

Purpose4/5

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

The description clearly states it retrieves detailed execution breakdown for a trade ID. However, it does not distinguish from sibling tools like get_trade_history or get_allocation_breakdown, which may overlap in functionality.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description implies it's for a specific trade ID but does not specify conditions or exclusions.

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