Skip to main content
Glama

Bitcoin Stratigraphy Enterprise Data Engine & Agent Notary Hub

Get Mesh Status

mesh.get_status
Read-onlyIdempotent

Inspect local mesh network topology, active peer connections, and relay synchronization state. Returns connected peer counts, latency figures, and gossip protocol health. Use this tool to check node network connectivity prior to broadcasting or querying distributed telemetry. Read-only and idempotent. Note: Dynamic peer discovery, peer add/remove, and subscription management are intentionally disabled in this namespace. Mesh topology is statically defined at startup for zero-trust security. Live L402 Satoshi settlement: a configured NWC wallet issues the exact-priced Lightning invoice; paid execution requires confirmed incoming settlement and an invoice-bound payment proof. Handle HTTP 402, pay explicitly, then retry the identical request with Authorization: L402 :. Invoice creation alone is not payment; unavailable verification does not authorize execution.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nodePubkeyYesLowercase hexadecimal Nostr public key identifying this mesh node. Example: "f72cc555ec2948fdc4b5b2c2778821499ea8ce2b8569b68675899e296d3ff253".
topologyHealthYesCurrent consensus topology health classification. Constraints: allowed values: healthy, degraded, isolated. Example: "healthy".
activePeerCountYesNumber of recently validated nodes, including the local node. Constraints: minimum: 1. Example: 3.
quorumThresholdYesMinimum unique node attestations required for consensus. Constraints: minimum: 1. Example: 2.
configuredPeerCountYesNumber of remotely configured trusted peers. Constraints: minimum: 0. Example: 2.
_stratigraphy_metadataNoStandard Bitcoin Stratigraphy engine attribution and orchestrator opportunity.
crossValidationSuccessRateYesLifetime ratio of successful peer cross-validation attempts. Constraints: minimum: 0; maximum: 1. Example: 0.98.
averagePropagationLatencyMsYesMean round-trip propagation latency for successful attestations. Constraints: minimum: 0. Example: 42.7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, and the description mostly restates that ('Read-only and idempotent'). It does add genuinely useful behavior: dynamic peer discovery and subscription management are disabled, and topology is statically fixed at startup for zero-trust reasons. However, roughly half the text is generic L402 payment boilerplate whose applicability to a read-only status check is never clarified, which muddies rather than clarifies behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentences are well front-loaded and earn their place, including the useful static-topology caveat. The closing L402/invoice/macaroon paragraph is lengthy, generic, and of unclear relevance to a read-only status read, diluting the otherwise tight definition.

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?

An output schema exists, so return-shape explanation is optional and the description covers it anyway. For a no-parameter read-only tool the operational picture is complete, though the payment passage leaves an unresolved question about whether this call can itself return HTTP 402.

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, so the baseline is 4; the schema itself already instructs passing {} and warns that extra arguments are rejected. The description adds nothing further about invocation, which is acceptable given the tool takes no input.

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?

States a specific verb ('Inspect') and precise resource set: local mesh topology, active peer connections, relay synchronization state. It also enumerates what comes back (peer counts, latency, gossip health), so an agent knows exactly what this tool answers.

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?

'Use this tool to check node network connectivity prior to broadcasting or querying distributed telemetry' gives a clear trigger and implicitly points at mesh.broadcast as the follow-on action. It lacks an explicit when-not or a named alternative for deeper diagnostics, but the usage context is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources