Skip to main content
Glama

Prexel Markets Pro

Domain evidence

get_domain_evidence
Read-onlyIdempotent

Inspect retained domain data in one BTC capture. Use path to expand a returned child key; JSON pointer escaping applies. A missing value stays unknown.

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>",
      "domain": "<domain>"
    },
    "name": "get_domain_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoJSON pointer into retained evidence.
domainYesDomain to inspect in the pinned capture.
offsetNoEntry offset for a paged path.
cycle_idYesExact cycle_id returned by get_synthesis; required for follow-ups.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds real value beyond them: data is 'retained' in a fixed capture (stable across calls), child keys can be expanded via path, and 'a missing value stays unknown' signals absence is reported rather than errored or fabricated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero filler; the core action comes first, then the path mechanics, then the null-handling rule. Every sentence carries distinct information.

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?

No output schema exists, yet the description hints at the return shape (child keys, unknown values) and the paging model is covered by the offset parameter's own schema text. For a read-only, fully-documented-parameter tool this is close to sufficient; only the concrete form of a returned evidence entry is left implicit.

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 coverage is 100%, so all four parameters are already documented, establishing a baseline of 3. The description adds a small amount beyond it by clarifying that path performs recursive expansion into returned child keys and that JSON pointer escaping applies — meaning not documented in the schema's 'JSON pointer into retained evidence' line.

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 — 'Inspect retained domain data in one BTC capture' — scoping it to a single pinned capture, which distinguishes it from a live/aggregate read. It does not contrast itself with siblings such as get_signal_evidence or get_synthesis, so the agent must infer the boundary from the domain enum alone.

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?

Offers one concrete usage instruction — 'Use path to expand a returned child key' — which tells the agent how to drill into results rather than re-fetching. However, there is no explicit when-to-use versus get_signal_evidence or get_synthesis, and no statement of prerequisites beyond the cycle_id mention carried in the schema.

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