Skip to main content
Glama

Get node health

get_node_health
Read-onlyIdempotent

Check the health status of a MeshCore node, including identity, radio, battery, uptime, and packet stats. For the home node, omit the node parameter; for remote repeaters, provide a contact name or public-key prefix.

Instructions

Consolidated health snapshot for a node: identity, radio, battery, uptime/queue, and packet/radio stats. Omit node for the connected home node; pass a contact name or hex public-key prefix for a remote repeater (logs in and reads its status).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoa contact name or hex public-key prefix for a remote node; omit for the connected home node

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
nodeYes
publicKeyNo
roleNo
reachableYes
lastHeardMsNo
batteryNo
radioNo
uptimeSecsNo
txQueueLenNo
statsNo
deviceTimeMsNo
telemetryBytesNo
firmwareNo
locationNo
autoAddContactsNo
degradedNosub-calls that failed after retries; the snapshot is partial — the listed fields are absent
Behavior4/5

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

Annotations already provide readOnly, destructive, idempotent, and openWorld hints. The description adds valuable context about logging into remote nodes, which implies authentication needs. Does not mention rate limits or error conditions, but rated highly due to annotation coverage.

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 sentences, each concise and purposeful. The key usage guideline is front-loaded, and no extraneous information is present, making it easy to scan.

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

Completeness5/5

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

With an output schema present, no need to describe return values. The description covers purpose, parameter usage, and behavioral context comprehensively for a read-only health snapshot tool.

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?

Schema covers 100% with a clear description of the 'node' parameter. The description adds nuance: omission for home node, and provides intent for remote nodes, enhancing understanding beyond the schema definition.

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?

Clearly states 'consolidated health snapshot' and lists specific data categories (identity, radio, battery, uptime/queue, packet/radio stats). Distinguishes from siblings by focusing on a comprehensive health overview rather than specific details.

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

Usage Guidelines5/5

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

Explicitly tells when to omit the parameter (home node) and when to provide it (remote repeater), with instructions on inputs. Provides context on the remote behavior (logs in and reads status), helping decide between this and other 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/dpup/meshcore-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server