Skip to main content
Glama

SODAX Builders MCP

by io.github.gosodax
OverviewDiscussionsAdmin

sodax_get_orderbook

Read-only

Get current orderbook entries showing pending/open intents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default server-side, cap 500)
formatNoResponse format: 'json' for raw data or 'markdown' for formatted textmarkdown
offsetNoOffset for simple pagination
creatorNoFilter by creator address
dstChainNoFilter by destination chain id
srcChainNoFilter by source chain id
inputTokenNoFilter by input token address
outputTokenNoFilter by output token address
deadlineAfterNoOnly return intents with deadline > value (Unix seconds)
deadlineBeforeNoOnly return intents with deadline < value (Unix seconds)
excludeZeroDeadlineNoExclude intents where deadline = 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / creator
      Added value: +{
+  "description": "Filter by creator address",
+  "type": "string"
+}
    • addedInput schema / properties / deadlineAfter
      Added value: +{
+  "description": "Only return intents with deadline > value (Unix seconds)",
+  "type": "number"
+}
    • addedInput schema / properties / deadlineBefore
      Added value: +{
+  "description": "Only return intents with deadline < value (Unix seconds)",
+  "type": "number"
+}
    • addedInput schema / properties / dstChain
      Added value: +{
+  "description": "Filter by destination chain id",
+  "type": "number"
+}
    • addedInput schema / properties / excludeZeroDeadline
      Added value: +{
+  "description": "Exclude intents where deadline = 0",
+  "type": "boolean"
+}
    • addedInput schema / properties / inputToken
      Added value: +{
+  "description": "Filter by input token address",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"REQUIRED: Maximum number of orders to return (1-100)"New value: +"Max results (default server-side, cap 500)"
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +500
    • changedInput schema / properties / offset / description
      Previous value: -"REQUIRED: Number of orders to skip for pagination"New value: +"Offset for simple pagination"
    • addedInput schema / properties / outputToken
      Added value: +{
+  "description": "Filter by output token address",
+  "type": "string"
+}
    • addedInput schema / properties / srcChain
      Added value: +{
+  "description": "Filter by source chain id",
+  "type": "number"
+}
    • removedInput schema / required
      Removed value: -[
-  "limit",
-  "offset"
-]
  2. Changed4 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -20
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of orders to return (1-100)"New value: +"REQUIRED: Maximum number of orders to return (1-100)"
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "REQUIRED: Number of orders to skip for pagination",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / required
      Added value: +[
+  "limit",
+  "offset"
+]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds that entries are 'pending/open intents', providing some behavioral context. However, it does not disclose pagination behavior, default response format, or how the orderbook is scoped, though the schema largely covers parameters.

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, front-loaded sentence with no redundant words. It succinctly states the tool's purpose without repeating schema or annotation information, demonstrating excellent conciseness.

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?

Given the tool has 11 optional parameters and no output schema, the one-sentence description is functional but minimal. It does not mention that filters are available, that the default response format is markdown, or how to retrieve a specific intent for more detail. The 'pending/open intents' phrase adds some value but leaves gaps for richer context.

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%, meaning all 11 parameters already have descriptive text in the schema. The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 uses a specific verb 'Get' with the resource 'current orderbook entries' and clarifies 'showing pending/open intents'. This clearly distinguishes it from sibling tools like sodax_get_intent, which likely retrieves a single intent, and other generic get_* tools.

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?

The description offers no guidance on when to use this tool versus alternatives. It lacks any mention of prerequisites, exclusions, or context where another tool (e.g., sodax_get_intent) would be more appropriate. The only usage signal is the tool name itself.

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

All SODAX Builders MCP toolsInspect
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.

Resources