Sera MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

cancel_order

Cancel an open order by providing its order ID and the owner's wallet address. This removes the order from the Sera exchange.

Instructions

Cancel an open order by its order ID.

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

Input Schema

Name	Required	Description	Default
`order_id`	Yes	The order ID to cancel
`owner_address`	Yes	Wallet address that owns the order

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

B3.1/5.0

Behavior1/5

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It does not mention side effects (e.g., order becomes inactive), reversibility, error conditions (e.g., if order is already canceled), or permissions required. The tool is a mutation but no such context is given.

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 a single, concise sentence with no redundancy or filler. It is front-loaded with the action and resource, effectively conveying the purpose in minimal words.

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

Completeness3/5

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

The tool is simple, and the description covers the basic action and parameters. However, with no output schema and no annotations, it lacks details on behavior after cancellation, failure modes, or validation. It is minimally viable but has clear gaps in contextual depth.

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% for both parameters, each with clear descriptions. The description adds no additional semantic meaning beyond the schema, which is acceptable given the high coverage.

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 action ('Cancel') and the resource ('open order') along with the key identifier ('order ID'). It is specific and distinguishes itself from sibling tools like place_limit_order or get_open_orders.

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 is provided on when to use this tool versus alternatives, prerequisites, or conditions such as the order being open. The description only states what it does, leaving the agent to infer usage.

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