Skip to main content
Glama
Sign In
Ophis

Ophis

Official
by ophis-fi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

submit_order

Relay a pre-signed order to the Ophis orderbook. Provide the order object, EIP-712 signature, and owner address to receive the order UID.

Instructions

Relay a PRE-SIGNED order to the chain's Ophis orderbook. Pass the exact order object and fullAppData from build_order, plus your EIP-712 signature and from (owner). The MCP holds no keys — it only forwards. Returns the order UID on success.

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": {
      "chainId": "<chainId>",
      "order": "<order>",
      "signature": "<signature>",
      "from": "<from>",
      "fullAppData": "<fullAppData>"
    },
    "name": "submit_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdYesEVM chain id the order was built for.
orderYesThe order object returned by build_order.
signatureYes0x EIP-712 signature over the order by the owner.
signingSchemeNoSignature scheme over the order (default 'eip712').
fromYesThe owner address that signed.
fullAppDataYesThe fullAppData string returned by build_order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description bears full burden. It discloses the forwarding nature and keyless operation, but lacks details on failure behavior, error responses, or rate limits. The return value is mentioned succinctly.

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?

Two sentences, fully front-loaded, no redundant information. Every sentence contributes essential guidance.

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

Completeness4/5

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

Despite no output schema and nested objects, the description covers the tool's purpose, input sources, and key constraint (pre-signed). It lacks examples or error scenarios, but is sufficient for an agent familiar with the domain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds workflow context by linking parameters to build_order outputs ('Pass the exact order object and fullAppData from build_order'), which helps the agent understand the data flow beyond schema definitions.

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 tool relays a pre-signed order to the Ophis orderbook, specifying the exact inputs (order, fullAppData from build_order, signature, from). It differentiates from sibling tools like build_order and get_quote by explicitly noting the pre-signed requirement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains that inputs must come from build_order and that the tool only forwards (holds no keys). However, it does not explicitly state when to use this tool vs alternatives or provide exclusions, leaving the agent to infer the workflow order.

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