Skip to main content
Glama
Sign In
shoonya-mcp

shoonya-mcp

by benatcmathew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_order_status

Retrieve the current status of a specific order by providing its order ID. This helps track order progress and confirm execution.

Instructions

Fetch the status of a specific order from the order book.

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

Input Schema

NameRequiredDescriptionDefault
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only says 'fetch', implying read-only, but does not confirm non-destructiveness, required permissions, or any side effects. The behavioral profile is minimally disclosed.

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

Conciseness4/5

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

The description is a single sentence of 10 words, efficient and front-loaded. However, it may be too brief to provide adequate context, sacrificing completeness for conciseness.

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?

Given the tool has one parameter, no output schema, and no annotations, the description should compensate. It does not explain what the response includes, any prerequisites (e.g., order must exist), or error conditions. The agent has insufficient information to fully understand invocation context.

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?

The schema has one parameter order_id with 0% description coverage. The description adds no information about the parameter's format, source, or constraints beyond the schema. The parameter semantics are entirely absent.

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 uses a specific verb 'Fetch' and resource 'status of a specific order', clearly distinguishing it from sibling tools like get_order_book (fetches all orders) or cancel_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 explicit guidance on when to use this tool versus alternatives such as get_order_book or check_margin. The description implies it is for checking a single order's status, but does not contrast with other tools.

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