edgex-mcp

edgex_set_leverage

Set leverage for an EdgeX perpetual contract using cross-margin. Provide symbol and leverage between 1 and 100 to adjust risk.

Instructions

Set leverage for a contract. EdgeX uses cross-margin mode.

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>",
      "leverage": "<leverage>"
    },
    "name": "edgex_set_leverage"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	e.g. BTC, ETH, SOL
`leverage`	Yes	Leverage multiplier (1-100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.8Aug 9, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It notes cross-margin mode but fails to mention prerequisites, effects on existing positions, reversibility, or response behavior. This is a significant gap for a mutation 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 exceptionally concise, using two short sentences. It is front-loaded with the primary action and includes only essential context about margin mode, with zero wasted words.

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?

Despite the tool's simplicity, the absence of annotations and output schema leaves important contextual gaps. The description does not explain what happens after setting leverage, whether it affects open positions, or what the tool returns, making it incomplete for a mutation operation.

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?

Schema description coverage is 100% with both 'symbol' and 'leverage' documented. The description adds no parameter-level details beyond the schema, so the baseline of 3 applies.

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 'Set' and the resource 'leverage for a contract', making the purpose unambiguous. It also adds context that EdgeX uses cross-margin mode, which helps differentiate it from other trading operations among the sibling tools.

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 description implies this tool is used to set leverage, but it does not explicitly state when to use it versus alternatives or provide exclusions. Since no other sibling tool sets leverage, the usage context is clear but not explicitly articulated.

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

Deploy Server