Skip to main content
Glama

nodus_pricing

View pricing details and access instructions for AI-powered Oracle signals used in prediction markets. Pay $1 USDC to obtain a session token for querying market signals.

Instructions

View NodusAI pricing and how to get started. Pay $1 USDC on nodusai.app → get a session token → use it for 3 Oracle signal queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function `nodusPricing` returns the pricing information and usage instructions for the NodusAI Oracle tool.
    export async function nodusPricing() {
      return ok({
        message: "NodusAI Oracle — Pricing & How to Connect",
        pricing: {
          cost:            "$1 USDC = 3 Oracle signal queries",
          pricePerQuery:   "$0.33 USDC",
          networks:        ["Base", "Ethereum", "Avalanche"],
          token:           "USDC",
        },
        howToGetStarted: [
          "1. Visit https://nodusai.app",
          "2. Connect your wallet (Base, Ethereum, or Avalanche)",
          "3. Paste a Polymarket or Kalshi market URL",
          "4. (Optional) Add your desired outcome",
          "5. Pay $1 USDC and confirm the transaction",
          "6. Copy your session token",
          "7. Use nodus_get_signal here with your session token",
        ],
        sessionDetails: {
          queriesPerPayment: 3,
          validity:          "24 hours",
          note:              "One session token = 3 queries. After 3 queries, visit nodusai.app to pay again.",
        },
        paymentUrl: "https://nodusai.app",
      });
    }
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses critical behavioral context: external payment requirement ($1 USDC), external domain interaction (nodusai.app), token mechanics, and rate limits (3 queries per dollar). Sufficient for a zero-param info tool.

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?

Two dense sentences with zero waste. Arrow notation efficiently conveys procedural flow. Front-loaded with purpose, followed by specific mechanics.

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?

Appropriate for a zero-parameter informational tool. Explains cost structure and onboarding workflow comprehensively. Minor gap: doesn't specify output format (text vs structured), but sufficient given low complexity.

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?

Zero parameters present; per scoring rules, baseline is 4. No additional parameter semantics required or possible to add.

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?

Specific verb 'View' + resource 'NodusAI pricing' clearly identifies the tool's function. Distinguishes decisively from operational siblings (get_signal, query_history, etc.) by identifying itself as the informational/pricing entry point.

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

Usage Guidelines4/5

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

Establishes clear workflow dependency: explains the payment-token-query chain ('Pay $1 USDC → get session token → use for 3 Oracle signal queries'), implicitly guiding users to invoke this before paid operations. Lacks explicit 'when not to use' language.

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