Skip to main content
Glama

nodus_admin_queries

Access administrative query data from the NodusAI MCP server to manage and analyze prediction market information for Polymarket and Kalshi platforms.

Instructions

[ADMIN] Full query registry dump.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • The handler function for the 'nodus_admin_queries' tool, which retrieves a list of queries from the registry.
    // ── 6. nodus_admin_queries ─────────────────────────────────────────────────────
    export async function nodusAdminQueries({ limit }) {
      return ok({ message: "NodusAI Query Registry", queries: getAllQueries(limit || 50) });
    }
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. The [ADMIN] prefix hints at authorization requirements and 'dump' implies read-only bulk retrieval, but there is no disclosure regarding pagination behavior, default limits, performance impact of a full dump, or output format.

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?

Extremely concise at only four words with zero filler text. The [ADMIN] tag is appropriately front-loaded to signal privilege requirements immediately. However, the brevity crosses into under-specification given the lack of schema descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter administrative tool with no output schema and no annotations, the description provides only the bare minimum functional identifier. It fails to explain the scope of the registry, return structure, or the undocumented limit parameter, leaving significant gaps for an admin-level tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% description coverage for the 'limit' parameter, and the description makes no mention of this parameter whatsoever. With zero schema documentation, the description fails to compensate by explaining what 'limit' constrains (e.g., number of queries, registry entries) or its default behavior when omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the tool performs a 'Full query registry dump' with an [ADMIN] prefix indicating privileged access, which specifies verb and resource. However, it fails to differentiate from sibling 'nodus_query_history' which also relates to queries, leaving ambiguity about when to use which.

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 (e.g., when to dump registry vs. query history), no prerequisites mentioned beyond the implicit [ADMIN] tag, and no warnings about the 'limit' parameter usage.

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