Skip to main content
Glama
Sign In
shoonya-mcp

shoonya-mcp

by benatcmathew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

modify_order

Modify an existing open order by updating quantity, price type, or price. Specify the order ID, exchange, and trading symbol.

Instructions

Modify an existing open 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>",
      "exchange": "<exchange>",
      "tradingsymbol": "<tradingsymbol>"
    },
    "name": "modify_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceNo
exchangeYes
order_idYes
quantityNo
price_typeNo
tradingsymbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations provided, and the description only says 'modify', which implies mutation but doesn't disclose potential side effects, permission requirements, or what happens if the order is not open. Minimal behavioral context.

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?

Extremely short but at the cost of omitting crucial details. While concise in word count, it fails to provide informative content, earning a low score for sacrificing information.

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?

With six parameters, no output schema, and no annotations, the description is entirely insufficient. It lacks any information about return values, error handling, prerequisites, or behavioral context, making it inadequate for an AI agent.

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 tool description does not explain any parameters. The agent must infer meaning from parameter names alone, which is insufficient for six parameters.

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?

Description clearly states the action (modify) and object (existing open order), distinguishing it from creation or cancellation. However, it doesn't specify what aspects can be modified or differentiate from similar tools like exit_order.

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 like cancel_order or exit_order. Only implies it applies to open orders, but no explicit when-not or prerequisite information.

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