Skip to main content
Glama
Sign In
@ainize/mcp

@ainize/mcp

Official
by ainblockchain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Node status

node_status
Read-only

Checks whether a shared model is free, who hosts it, server capabilities, and remaining live-test quota before spending; refresh after a model-busy failure.

Instructions

What this node is, whether the shared model is free and who holds it, what this MCP server is allowed to do (capabilities), the free live-test quota as last observed, and the teach policy. Call it when a job says the model is busy, or before spending anything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "node_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoforce a live probe of the model server, and re-derive what this server can do from what the node answers — call it after a live test failed because the model server was down (adds up to ~3 s)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint and openWorldHint already tell the agent this is a safe, externally-probing read. The description adds two useful things beyond that: the quota is 'as last observed' (i.e. possibly stale) and the capabilities view is a permission-derived snapshot. It does not describe response shape, and the ~3 s cost of a live probe lives in the schema, not here, so credit is limited.

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?

Contents are front-loaded, followed by the call conditions, and nothing is redundant. The first sentence is a long comma-chained list, which is dense but still parseable. Slight trimming of the capability parenthetical would tighten it.

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?

With no output schema, the description must carry the return contents, and it does: it names all five things the agent will get back. Combined with annotations covering safety, that is nearly everything needed to decide to call it and interpret the result. Field-level formats and how to read the teach policy remain unspecified.

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 coverage is 100% and the single optional refresh parameter is documented there, including its cost and the failure scenario that motivates it. The description adds no parameter meaning of its own — 'as last observed' hints at the cached-vs-live distinction but does not connect it to refresh explicitly. Baseline 3 applies.

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 enumerates a specific resource set: node identity, shared-model availability and holder, server capabilities, live-test quota, and teach policy. That is far more specific than the title, and none of the sibling names suggest this introspection surface. It falls short of 5 only because the verb is implicit — it lists what the tool reports rather than saying plainly that it returns a single status snapshot.

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?

Gives two concrete triggers: when a job reports the model is busy, and before spending anything (quota). That is actionable, conditional guidance an agent can key on. There is no explicit when-not or named alternative, so it stops short of 5.

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

Deploy Server

Other Tools