Skip to main content
Glama
Sign In
TradeStaq MCP

TradeStaq MCP

Official
by the-staq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

close_position

Execute a market order to close an open trading position. Requires trade ID, exchange ID, and symbol.

Instructions

Close an open trading position. WARNING: This executes a market order to close your position.

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": {
      "tradeId": "<tradeId>",
      "exchangeId": "<exchangeId>",
      "symbol": "<symbol>"
    },
    "name": "close_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTrading pair (e.g. BTC/USDT)
tradeIdYesTrade/position ID to close
exchangeIdYesExchange account ID where the position is open
percentageNoPercentage of position to close (100 = full close)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Description discloses that the tool executes a market order, which is a key behavioral trait beyond the lack of annotations. However, it omits other important details like irreversibility, required permissions, or post-close effects.

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?

Extremely concise: two sentences front-loading the main action and a critical warning. Every sentence provides essential information with no waste.

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 dangerous nature (market order), the description lacks details on expected outputs, error conditions, or prerequisites. An agent would need more context for safe use.

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 coverage is 100% with descriptions for all parameters. The tool description adds no additional meaning or usage context to the parameters.

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 'Close an open trading position' uses a specific verb and resource, clearly stating the tool's function. It distinguishes itself from sibling tools like get_positions by indicating it performs an action rather than retrieval.

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 versus alternatives. The warning about market order execution gives some context but does not specify when not to use or mention alternative tools like limit 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