Skip to main content
Glama

nodus_verify_signal

Retrieve grounding sources to verify Oracle reasoning for prediction market signals by providing a query ID from previous signal calls.

Instructions

Retrieve grounding sources for a past signal to verify the Oracle's reasoning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryIdYesqueryId from a previous nodus_get_signal call

Implementation Reference

  • The handler function that executes the logic for verifying a signal by queryId.
    export async function nodusVerifySignal({ queryId }) {
      if (!queryId) return err("queryId is required");
      const all   = getAllQueries(1000);
      const entry = all.find(q => q.id === queryId);
      if (!entry) return err(`Query ${queryId} not found`);
      if (!entry.success || !entry.signal) return ok({ queryId, verified: false, reason: "No signal for this query" });
    
      return ok({
        queryId,
        verified:          true,
        marketUrl:         entry.marketUrl,
        platform:          entry.platform,
        desiredOutcome:    entry.desiredOutcome || null,
        timestamp:         entry.timestamp,
        signal: {
          market_name:       entry.signal.market_name,
          predicted_outcome: entry.signal.predicted_outcome,
          probability:       entry.signal.probability,
          confidence_score:  entry.signal.confidence_score,
          key_reasoning:     entry.signal.key_reasoning,
        },
        grounding_sources: entry.signal.grounding_sources,
        note: "Verify these sources independently to audit the Oracle's reasoning.",
      });
    }
Behavior3/5

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

With no annotations provided, the description carries full disclosure burden. It identifies the operation as a retrieval and mentions the domain concept ('grounding sources'), but omits safety profile (idempotency, rate limits), data retention policies, or what format/structure the grounding sources take.

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?

Single 12-word sentence with zero waste. Front-loaded with the action verb 'Retrieve,' immediately communicating the tool's function without filler or redundancy.

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 single-parameter retrieval tool without output schema, the description adequately covers the core intent but leaves significant gaps: it does not explain what 'grounding sources' contain (citations, documents, confidence scores) or hint at the return structure, which would be valuable given the absence of an output schema.

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%, documenting that queryId comes from a previous nodus_get_signal call. The description references 'past signal' which conceptually aligns with this parameter reference, but adds no syntax, format details, or examples beyond the schema baseline.

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?

The description provides a specific verb ('Retrieve'), resource ('grounding sources'), and scope ('for a past signal'). It distinguishes from nodus_get_signal by emphasizing 'verify' and 'past signal' versus getting a new signal, though it could explicitly name the sibling relationship.

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 implied through 'to verify the Oracle's reasoning' and 'past signal,' suggesting this is for auditing existing results rather than new queries. However, there is no explicit 'Use this when...' guidance or direct comparison to nodus_get_signal in the description text (only in the schema).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NodusAI-Your-Prediction-Broker/nodusai-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server