Skip to main content
Glama

Intent Book — Order Evals

sv_intents
Read-only

Live per-order evaluation records from the Orkid DLN listener fleet and graph-router path evaluator: give/take chains+tokens+amounts, USD values, cost, margin_bps — the same book our policy engine reads. Params: src (dln|path), min_bps, limit, since_min. Sorted by margin desc. Free with X-ORKID-API-Key or $0.005 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_intents"
  }
}

Input Schema

NameRequiredDescriptionDefault
srcNoSource filter: "dln" or "path"
limitNoMax records
min_bpsNoMinimum margin_bps
since_minNoOnly records newer than N minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the bar is lower, and the description still adds real behavior: results are sorted by margin descending, data is live from a listener fleet, and access requires an X-ORKID-API-Key or a $0.005 USDC x402 payment. Pagination and default limit behavior are not disclosed, keeping it short of 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?

Two dense sentences, front-loaded with what the data is before the params and access terms. Domain jargon ('DLN listener fleet', 'graph-router path evaluator') costs some clarity but each clause carries information an agent needs.

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?

With no output schema, the description compensates by enumerating the returned fields (give/take chains, tokens, amounts, USD values, cost, margin_bps) and the sort order. Combined with the auth/pricing note and full schema coverage on inputs, an agent has what it needs to call this correctly.

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 all four parameters are already documented, and the description mostly restates them (src dln|path, min_bps, limit, since_min). It adds no format, unit, or default details beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: it returns live per-order evaluation records from the DLN listener and graph-router path evaluator, and enumerates the payload (give/take chains, tokens, amounts, USD values, cost, margin_bps). The 'per-order evaluation' framing plus the src dln|path split makes it distinguishable from the quote/swap siblings, though it never names an alternative directly.

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?

Usage is only implied: the min_bps filter and margin-desc ordering suggest it is for scanning high-margin order evaluations, and 'the same book our policy engine reads' hints at parity use. There is no explicit when-to-use, when-not-to-use, or reference to any sibling tool such as orkid_quote or sv_uniswapx.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources