Skip to main content
Glama
NodusAI-Your-Prediction-Broker

nodusai-mcp-server

by NodusAI-Your-Prediction-Broker
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

nodus_admin_stats

Monitor platform usage statistics including total queries and breakdown by platform for administrative oversight.

Instructions

[ADMIN] Platform stats: total queries, breakdown by platform.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/index.js:210-212 (handler)
    The implementation of the nodus_admin_stats tool.
    export async function nodusAdminStats() {
  return ok({ message: "NodusAI Platform — Registry Stats", ...getStats() });
}
  • src/index.js:102-105 (registration)
    The tool definition and schema registration for nodus_admin_stats.
      name: "nodus_admin_stats",
  description: "[ADMIN] Platform stats: total queries, breakdown by platform.",
  inputSchema: { type: "object", properties: {} },
},
  • src/index.js:121-121 (registration)
    Mapping the tool name to its handler implementation in HANDLERS object.
    nodus_admin_stats:   nodusAdminStats,

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full disclosure burden. It successfully indicates the return data structure (aggregate totals and platform breakdowns) but omits safety details like read-only nature, rate limits, or authentication requirements beyond the '[ADMIN]' hint.

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?

Every word earns its place: the '[ADMIN]' tag immediately scopes privilege level, 'Platform stats' declares the action and resource, and 'total queries, breakdown by platform' specifies the return data. Zero redundancy in a single efficient sentence.

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?

Given the tool's simplicity (zero parameters) and lack of output schema, the description adequately explains what data will be returned (aggregated statistics). It could be improved by noting whether data is real-time or cached.

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?

The input schema contains zero properties with 100% description coverage. Per the baseline rules for zero-parameter tools, this earns a default score of 4 since no parameter explanation is required.

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?

The description '[ADMIN] Platform stats: total queries, breakdown by platform' provides a specific verb (stats), clear resource (platform), and distinguishes itself from siblings like nodus_get_signal (individual records) and nodus_query_history (historical logs vs aggregate statistics).

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?

The '[ADMIN]' prefix implies administrative context and privilege requirements, but there is no explicit guidance on when to use this versus nodus_admin_queries or other sibling tools, nor when not to use it.

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