edgex-mcp

edgex_get_max_size

Determine the maximum order size for a perpetual contract based on your current balance and leverage to avoid exceeding trading limits.

Instructions

Get maximum order size for a contract given current balance and leverage.

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": {
      "symbol": "<symbol>"
    },
    "name": "edgex_get_max_size"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	e.g. BTC, ETH, SOL

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.8Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are present, so the description bears full responsibility for disclosing behavioral traits. It does not mention read-only status, authentication requirements, side effects, or return format. The dependency on balance and leverage is mentioned but without explaining how these factors influence the result or what happens if data is unavailable.

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, concise sentence that front-loads the action and resource. No unnecessary words or redundancy, making it easy to parse quickly.

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?

There is no output schema, so the description should clarify what the returned maximum order size represents (e.g., units, base vs quote asset). The description is brief and leaves ambiguity, and with no annotations to supplement context, an agent may not know how to interpret the result.

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

Parameters3/5

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

The input schema has 100% coverage for the only parameter 'symbol', with an example provided. The description adds no additional meaning to this parameter, so the baseline score of 3 applies since the schema sufficiently documents 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 tool's function: retrieving the maximum order size for a contract. The verb 'Get' and specific resource 'maximum order size' make it distinct from sibling get_* tools, which focus on other data like ticker, depth, or balances.

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

Usage Guidelines3/5

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

The phrase 'given current balance and leverage' implies the tool is used to assess order capacity based on account state, but no explicit guidance is provided on when to use this tool versus alternatives. Exclusions or alternative tool references are absent, leaving usage only implied.

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

Deploy Server