Armor Crypto MCP

Official

Overview Schema Source Related Servers Discussions Admin

create_order

Place limit, take profit, or stop loss orders on crypto tokens by specifying amount, wallet, target value, and watch conditions.

Instructions

Create a order. Can be a limit, take profit or stop loss order.

Expects a CreateOrderRequestContainer, returns a CreateOrderResponseContainer.

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": {
      "create_order_requests": "<create_order_requests>"
    },
    "name": "create_order"
  }
}

Input Schema

Name	Required	Description	Default
`create_order_requests`	Yes

Output Schema

Name	Required	Description	Default
`create_order_responses`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2025

TDQS

C2.9/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 fully disclose behavior. It mentions input/output container types but does not describe side effects (e.g., order lifecycle, wallet impact), authentication needs, or constraints. Minimal transparency.

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?

Two concise sentences with no wasted words. However, it could be restructured to front-load the most critical info (order types) more clearly.

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's complexity (many parameters, nested objects, multiple order types), the description is too brief. It does not explain when to use each order type, how parameters interact, or what the output looks like. Output schema exists but description does not leverage it.

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?

The input schema has detailed descriptions for most nested properties, so schema coverage is effectively high even though top-level schema has no descriptions. The description adds minimal extra meaning beyond listing order types. Baseline 3 is appropriate.

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?

Clearly states it creates an order and lists specific order types (limit, take profit, stop loss). Differentiates from sibling tools like cancel_order, list_orders, and create_dca_order by specifying the action and types.

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 create_order versus alternatives such as create_dca_order or swap_quote. No when-not-to-use or prerequisite information.

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