oddsrail

server_info

Read-onlyIdempotent

Check server status before first trade: view dry-run state, attribution config, enabled capabilities, venue reachability, and IP geoblock advisory. Ensures readiness for session.

Instructions

Server status: dry-run state, attribution config, enabled capabilities, venue reachability from this machine, and Polymarket's geoblock verdict for this machine's IP (advisory — not a compliance check). Call this before the first order of a session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "server_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.18.1Sep 22, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "server_infoOutput",
-  "type": "object"
-}New value: +null

First observedv0.3.0Aug 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, non-destructive, and open-world. The description adds useful context beyond those hints: it lists exactly what status categories are included and clarifies that the Polymarket geoblock verdict is advisory only, not a compliance check. This helps the agent interpret the result correctly.

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 compact and front-loaded: it opens with 'Server status', lists the key components in a scannable manner, adds an important caveat, and closes with a clear instruction on when to call it. No sentence is wasted.

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

Completeness5/5

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

For a zero-parameter read-only status tool with no output schema, the description is complete. It tells the agent what information will be available, flags the advisory nature of the geoblock check, and states when to invoke the tool. There are no missing inputs or ambiguous actions.

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?

The tool has zero parameters, so there is nothing for the description to explain about inputs. The rubric's baseline for zero-parameter tools is 4, and the description appropriately focuses on behavior rather than parameter details.

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 identifies the resource as server status and enumerates the specific components included (dry-run state, attribution config, enabled capabilities, venue reachability, geoblock verdict). It does not use an explicit verb like 'get' or 'retrieve', and it does not explicitly compare itself to sibling tools, though its uniqueness among the trading tools is evident.

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?

The description gives explicit temporal guidance: 'Call this before the first order of a session.' This tells the agent when to use the tool. It does not mention when not to use it or name alternatives, but no sibling appears to offer the same server-status functionality.

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