Skip to main content
Glama
Sign In
shoonya-mcp

shoonya-mcp

by benatcmathew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

exit_order

Exit an open position by placing a market order in the opposite direction. Specify the order ID and product type to close the trade.

Instructions

Exit an open position by placing an opposite market order.

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": {
      "order_id": "<order_id>",
      "product_type": "<product_type>"
    },
    "name": "exit_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes
product_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

Without annotations, the description carries full burden. It states it places an opposite market order but omits prerequisites (e.g., authentication, margin), whether it closes the entire position, and effects on related orders.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but overly terse; it lacks necessary details about parameters and behavioral context, making it insufficient for an agent.

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

Completeness1/5

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

Given the complexity of a trading tool with two parameters and no output schema or annotations, the description fails to provide sufficient context for correct tool invocation.

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 description coverage is 0%, and the description provides no explanation for the two required parameters (order_id and product_type). An agent cannot infer their meaning or format from the description alone.

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?

Description clearly states the verb 'exit' with resource 'open position' and method 'opposite market order'. This distinguishes it from siblings like cancel_order (which cancels orders) and place_order (generic placement).

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 explicit guidance on when to use exit_order versus alternatives such as cancel_order or place_order. The purpose is implied but not contrasted.

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