Ophis MCP

submit_order

Destructive

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). Returns the order UID on success and enrolls the owner for indexing, referral attribution, and trade rewards.

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

Name	Required	Description
`from`	Yes	The owner address that signed.
`order`	Yes	The order object returned by build_order.
`chainId`	Yes	EVM chain id the order was built for.
`signature`	Yes	0x EIP-712 signature over the order by the owner.
`fullAppData`	Yes	The fullAppData string returned by build_order.
`signingScheme`	No	Signature scheme over the order (default 'eip712').

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / chainId / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / chainId / minimum
```
Added value: +-9007199254740991
```
- removedInput schema / properties / order / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / order / properties / validTo / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / order / properties / validTo / minimum
```
Added value: +-9007199254740991
```
Changed2 schema fields changedJun 17, 2026
- addedInput schema / properties / chainId / description
```
Added value: +"EVM chain id the order was built for."
```
- addedInput schema / properties / signingScheme / description
```
Added value: +"Signature scheme over the order (default 'eip712')."
```

Changed1 schema field changedJun 15, 2026

removedInput schema / properties / allowCustomReceiver

Removed value: -{
-  "description": "Required (true) to relay an order whose receiver is not the owner. Default refuses — drain guard.",
-  "type": "boolean"
-}

First observedJun 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With annotations already declaring the tool as non-read-only, destructive, and open-world, the description adds useful behavior: it returns the order UID on success and enrolls the owner for indexing, referral attribution, and trade rewards. It does not explain error handling or whether submission can be cancelled, but the main side effects are disclosed.

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 tightly written sentences with no waste. The key action and dependency are front-loaded, followed by success behavior and enrollment effects.

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?

For a complex nested-object submission tool with no output schema, the description covers the core prerequisites, the expected inputs, and the success return value. It leaves out error behavior and an explicit validation step with validate_order, but is otherwise sufficient.

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 the schema carries the detailed parameter definitions. The description adds semantic value by tying the order and fullAppData parameters to build_order and clarifying that from is the owner who signed; signingScheme is left to the schema.

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 states a specific verb and resource: relaying a pre-signed order to the Ophis orderbook. It distinguishes the tool from build_order by explicitly requiring a pre-signed order and naming build_order as the source of the order object.

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

Usage Guidelines4/5

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

It gives clear usage context by explaining that the order and fullAppData must come from build_order and that a signature and owner are required. However, it does not explicitly mention when to use validate_order first or describe failure conditions.

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

All Ophis MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.