Skip to main content
Glama
Undertow MCP

Undertow MCP

Consensus price when venues disagree

venue_price_reconciliation
Read-onlyIdempotent

Reconcile BTC/ETH venue prices using depth-weighted consensus, squared half-spread weights, and dislocation checks to flag concentration and deepest-venue blindness; read-only, no execution.

Instructions

BTC/ETH consensus: depth/squared-half-spread weights, deepest-venue blindness, concentration, dislocations. Experimental; no execution authority.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the safety profile is covered. The description does add real value beyond that by flagging the tool as 'Experimental' and stating it holds 'no execution authority', and the 'deepest-venue blindness' phrase hints at a known bias. What is missing is what the consensus actually returns or how disagreement is surfaced.

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?

One dense sentence plus a caveat clause, with the subject (BTC/ETH consensus) front-loaded and nothing padded. It loses a point because 'deepest-venue blindness' is too compressed to decode without domain background, so brevity tips into opacity.

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?

For a zero-argument, read-only calculation the description is nearly sufficient, and the listed terms (concentration, dislocations) hint at what the output may contain. But there is no output schema, and the description never states the return shape or that a consensus price is the primary output, leaving that to inference.

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 takes zero parameters, so there is nothing for the description to disambiguate; the schema is trivially complete at 100% coverage. The baseline of 4 applies for a no-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'BTC/ETH consensus' names the resource, and the title 'Consensus price when venues disagree' clarifies it is a cross-venue price aggregation. However, the description itself is a verbless keyword list ('depth/squared-half-spread weights, deepest-venue blindness, concentration, dislocations') rather than a stated function, and it never distinguishes itself from the sibling venue_concentration, whose concept it also lists as a component.

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?

The closing phrase 'Experimental; no execution authority' tells the agent not to rely on this for trade execution, which is a genuine usage caveat. But it names no alternative tool and gives no positive condition for when to reach for this over venue_concentration, liquidity_tiers, or depth_episodes.

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