Skip to main content
Glama

Score Signal Coherence — Coherent Gate

interfere
Destructive

Coherent Gate (PAID, x402/USDC). Scores whether your trading-signal paths agree: confidence-weighted long/short/flat consensus, coherence 0-1, and a pass/block gate (pass needs a non-flat consensus and coherence at or above the threshold, default 0.6). Tiers by path count: scout ≤4 $0.01, standard ≤8 $0.05, beast ≤32 $0.25 (defaults). The $0.25 max tier is charged upfront; on the x402 rail the unused difference is recorded as owed (not yet auto-refunded); on the Arc escrow rail (arc_auth_id) only the used tier is captured. Optional ticker pulls extra paths from registered sources before charging. Max 32 paths. Not financial advice.

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

Input Schema

NameRequiredDescriptionDefault
pathsNoCoherent Gate: AI trading signal paths to check for coherence. Priced tiers: scout ≤4, standard ≤8, beast ≤32 (defaults); >32 hard-rejected.
tickerNoOptional: pull extra paths for this ticker from registered path sources (see docs/COHERENT_GATE_PATH_SOURCES.md).
sourcesNoOptional path-source ids; default = all enabled verified sources. Requires ticker.
arc_auth_idNoArc rail: authId from AuthCaptureEscrow.authorize() for at least the max-tier amount to our receiver. Only the used tier is captured; the rest returns via reclaim() after expiry.
payment_headerNoBase64 X-PAYMENT EIP-3009 payload (standard rail).
wallet_addressNoAgent wallet address (informational).
payment_tx_hashNoBase USDC tx hash (sovereign rail).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / paths / items / properties / confidence / description
      Added value: +"Weight 0-1 this path gets in the consensus."
    • addedInput schema / properties / paths / items / properties / direction / description
      Added value: +"Direction this path calls: long, short, or flat."
    • addedInput schema / properties / paths / items / properties / source / description
      Added value: +"Label for where this signal came from (1-64 chars)."
  2. Changed5 schema fields changed
    • addedInput schema / properties / paths / default
      Added value: +[]
    • removedInput schema / properties / paths / minItems
      Removed value: -1
    • addedInput schema / properties / sources
      Added value: +{
      +  "description": "Optional path-source ids; default = all enabled verified sources. Requires ticker.",
      +  "items": {
      +    "maxLength": 64,
      +    "type": "string"
      +  },
      +  "maxItems": 16,
      +  "type": "array"
      +}
    • addedInput schema / properties / ticker
      Added value: +{
      +  "description": "Optional: pull extra paths for this ticker from registered path sources (see docs/COHERENT_GATE_PATH_SOURCES.md).",
      +  "pattern": "^[A-Z]{1,10}$",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "paths"
      -]
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds substantial context the annotations cannot convey: tiered USDC pricing, upfront charging of the $0.25 max tier, the fact that the unused difference is recorded as owed and not auto-refunded on the x402 rail, and that the Arc escrow rail captures only the used tier. It also discloses that an optional ticker pulls extra paths from registered sources before charging and that more than 32 paths are hard-rejected. Missing: whether the owed balance blocks future calls and whether charges recur per invocation beyond the non-idempotent hint.

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?

The definition is front-loaded with the core function and gate semantics before moving to pricing, and every sentence carries operational information. It is dense and parenthetical-heavy, and the closing 'Not financial advice' line is boilerplate, but there is no true padding.

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

Completeness4/5

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

For a seven-parameter, payment-bearing, non-idempotent tool with no output schema, the description is nearly sufficient: it characterizes the return values (consensus, coherence, gate) and the three payment rails. The remaining gap is the exact response shape and the consequences of carrying an unsettled owed balance.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning on top: it ties the paths array to pricing tiers by count, explains that ticker sources are resolved and merged before billing occurs, and clarifies that arc_auth_id must authorize at least the max-tier amount. These are behavioral semantics beyond the schema's field-level text.

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 opens with a concrete verb and resource: it scores trading-signal paths for coherence, returning a confidence-weighted long/short/flat consensus, a 0-1 coherence value, and a pass/block gate. The pass condition (non-flat consensus plus coherence at or above threshold, default 0.6) makes the output contract explicit, so an agent can tell this apart from spend_gate_check or precross_analyze without opening a schema.

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?

It implies the use case (validating signal agreement before acting) and states the gating condition, but never says when to prefer this over the sibling tools or when it would be inappropriate. No exclusions, prerequisites, or alternatives are named, so routing guidance is only implied.

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