Skip to main content
Glama
Sign In

Orkid Swap

by xyz.orkidlabs
OverviewDiscussionsAdmin

Futures Reference

sv_futures_ref
Read-only

Futures contract reference + mechanics: futures_products, futures_meta, futures_contracts, futures_schedules, futures_roll, futures_anchor_map, futures_sessions, futures_anchors, prop_constraints, apex_constraints. Price/volume columns stripped — specs and mechanics only. Params: panel, ticker, start/end, limit (default 100, max 500). Free with X-ORKID-API-Key or $0.01 USDC/call via x402.

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": "sv_futures_ref"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date YYYY-MM-DD
limitNoMax rows, default 100, cap 500
panelNoPanel to query (default first). Available: futures_products, futures_meta, futures_contracts, futures_schedules, futures_roll, futures_anchor_map, futures_sessions, futures_anchors, prop_constraints, apex_constraints
startNoStart date YYYY-MM-DD
tickerNoContract ticker for session panels

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safe read-only, non-destructive, open-world profile, but the description adds real context beyond them: the price/volume column exclusion, the default/cap limit behavior, and the auth/paid access paths (X-ORKID-API-Key or $0.01 USDC via x402). Return shape and row semantics are not described, keeping it below a 5.

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?

Content is front-loaded: purpose, panel list, the key data-scope caveat, then params and access. The panel enumeration is long but functional, and the only mild waste is repeating limit defaults already in the schema.

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?

With no output schema, the description should at least convey what the panels return, but it only names them. It does cover access/pricing and data scope, and all five params are optional, so it is adequate but leaves the agent guessing about row structure and cross-panel differences.

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%, so the schema already documents every parameter including panel enumerations, date formats, ticker, and limit default/cap. The description's param summary largely restates what the schema provides, adding no new meaning such as how panel selection interacts with ticker or dates.

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 opens with a specific verb+resource ('Futures contract reference + mechanics') and enumerates the exact panels exposed. It implicitly separates itself from the price-oriented sibling sv_futures via 'Price/volume columns stripped', though it never names that sibling explicitly.

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?

'Price/volume columns stripped — specs and mechanics only' hints that price data belongs elsewhere, effectively steering agents toward sv_futures. However, no sibling is named and no explicit when-to-use/when-not rule is stated, so usage is inferred rather than guided.

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

All Orkid Swap 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