Skip to main content
Glama
jarvismaximum-hue

ProfitPlay MCP Server

cancel

Cancel an open order in the ProfitPlay prediction market by specifying its order ID to manage active trades.

Instructions

Cancel an open order by order ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesThe order ID to cancel

Implementation Reference

  • Handler for the "cancel" tool. It calls the POST /api/order/cancel endpoint with the orderId argument.
    case "cancel":
      return { content: [{ type: "text", text: JSON.stringify(await apiPost("/api/order/cancel", { orderId: args?.orderId }), null, 2) }] };
  • src/index.ts:105-114 (registration)
    Registration of the "cancel" tool within the ListToolsRequestSchema handler.
      name: "cancel",
      description: "Cancel an open order by order ID.",
      inputSchema: {
        type: "object" as const,
        properties: {
          orderId: { type: "string", description: "The order ID to cancel" },
        },
        required: ["orderId"],
      },
    },
Behavior3/5

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

Without annotations, the description carries the burden of behavioral disclosure. It specifies the 'open' state requirement, implying the operation only works on active orders. However, it omits whether this is destructive, idempotent, reversible, or what state the order transitions to after cancellation.

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, efficient sentence that front-loads the action verb. No words are wasted; it conveys the essential operation and constraint with maximum brevity.

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?

For a single-parameter tool with complete schema coverage, the description adequately conveys core functionality. However, clear gaps remain: no output schema is described, no side effects are documented, and the lack of annotations for a state-mutating operation leaves the agent uncertain about safety and idempotency.

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%, establishing a baseline of 3. The description adds minimal value regarding the parameter itself (repeating 'order ID'), but implies validation logic (the ID must reference an 'open' order), which slightly augments the raw schema definition.

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?

The description clearly states the action ('Cancel') and target ('open order'), including the specific constraint that the order must be 'open'. However, it does not explicitly differentiate from sibling tools like 'bet' or 'market' regarding whether this cancels bets, market orders, or general game 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 provided on when to use this tool versus alternatives, prerequisites for cancellation, or conditions where cancellation might fail (e.g., if the order is already filled). The agent receives no explicit decision-making criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jarvismaximum-hue/profitplay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server