Skip to main content
Glama

nodus_query_history

Access your recent NodusAI oracle query history to review past predictions and analysis for Polymarket and Kalshi markets.

Instructions

View your recent NodusAI oracle query history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletAddressYesYour wallet address
limitNoMax records (default: 20)

Implementation Reference

  • The actual implementation of the nodus_query_history tool, which retrieves and formats query history for a given wallet address.
    export async function nodusQueryHistory({ walletAddress, limit }) {
      if (!walletAddress) return err("walletAddress is required");
      const agent = getAgentByWallet(walletAddress);
      if (!agent) return ok({ message: "No queries found for this wallet", queries: [] });
    
      const history = getQueryHistory(agent.id, limit || 20);
      return ok({
        agentId:       agent.id,
        walletAddress: agent.walletAddress,
        totalReturned: history.length,
        queries: history.map(q => ({
          queryId:          q.id,
          marketUrl:        q.marketUrl,
          platform:         q.platform,
          desiredOutcome:   q.desiredOutcome || null,
          predictedOutcome: q.signal?.predicted_outcome || null,
          probability:      q.signal?.probability ?? null,
          confidence:       q.signal?.confidence_score || null,
          success:          q.success,
          timestamp:        q.timestamp,
        })),
      });
    }
  • The registration and input schema definition for the nodus_query_history tool.
    name: "nodus_query_history",
    description: "View your recent NodusAI oracle query history.",
    inputSchema: {
      type: "object",
      properties: {
        walletAddress: { type: "string", description: "Your wallet address" },
        limit:         { type: "number", description: "Max records (default: 20)" },
      },
      required: ["walletAddress"],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal safety or operational context. While 'View' implies read-only, it doesn't confirm idempotency, mention authentication requirements beyond the wallet parameter, explain what 'recent' means temporally, or disclose pagination/sorting behavior.

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?

Single sentence with efficient front-loading (verb-first). No redundant or wasted text. However, given the absence of annotations and the presence of similar sibling tools, the brevity arguably contributes to under-specification rather than optimal clarity.

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?

Adequate for a low-complexity tool (2 flat parameters, no output schema) but leaves gaps due to missing annotations. The description identifies the return concept (history) but doesn't address scope limitations, error conditions, or the specific nature of 'oracle queries' within the NodusAI system.

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%, establishing a baseline of 3. The description adds 'your recent' which semantically links the walletAddress parameter to ownership and the limit parameter to recency, but this adds minimal explanatory value beyond the schema's own descriptions ('Your wallet address', 'Max records').

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?

Uses specific verb 'View' and identifies the resource as 'NodusAI oracle query history'. The possessive 'your' effectively distinguishes this user-scoped tool from the sibling 'nodus_admin_queries'. However, it doesn't clarify the relationship to 'nodus_get_signal' or 'nodus_verify_signal' which operate on similar domain objects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this tool versus siblings, particularly 'nodus_admin_queries'. It states what the tool does but offers no conditions, prerequisites (beyond the implicit wallet address), or workflow guidance for an agent navigating the available tools.

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