Skip to main content
Glama

Prexel Markets Pro

Signal evidence

get_signal_evidence
Read-onlyIdempotent

Read one captured signal and its raw operands from the specified BTC capture. Never combine different capture IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cycle_id": "<cycle_id>",
      "signal_id": "<signal_id>"
    },
    "name": "get_signal_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoJSON pointer into retained evidence.
offsetNoEntry offset for a paged path.
cycle_idYesExact cycle_id returned by get_synthesis; required for follow-ups.
signal_idYesExact signal_id from the pinned synthesis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds one genuinely useful behavioral constraint about not mixing capture IDs and mentions that raw operands are returned, but says nothing about paging behavior or response size.

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 short sentences with no filler, and the core action is front-loaded before the constraint. The second sentence is somewhat abrupt but does carry a real correctness warning.

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 four-parameter read tool with full schema coverage, annotations, and no output schema, most needed information is structured elsewhere. However, the description omits any hint about the paged path/offset retrieval flow, which is the one non-obvious part of the contract.

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 every parameter (cycle_id, signal_id, path, offset) is already documented in the schema. The description only loosely gestures at the capture/signal identifiers and adds no meaning for path or offset paging beyond what the schema provides, making baseline 3 appropriate.

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 (read) and a specific resource (one captured signal plus its raw operands) scoped to a single BTC capture. This distinguishes it from a broad synthesis tool, though it never explicitly contrasts with get_domain_evidence or get_synthesis.

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 only guidance is the constraint 'Never combine different capture IDs,' which is a usage rule rather than a when-to-use statement. There is no explicit indication of when an agent should prefer this over get_domain_evidence or get_synthesis, so selection must be inferred from the names.

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