Skip to main content
Glama

wot_network_health

Analyze Nostr network health metrics including node count, decentralization scores, and component analysis to assess network structure and stability.

Instructions

Get Nostr network health metrics: node count, edge count, Gini coefficient (decentralization), power-law exponent, density, and component analysis. No pubkey needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payment_hashNoPayment hash if free tier exhausted

Implementation Reference

  • The handler and registration for 'wot_network_health' tool. It calls wotGet to retrieve network health metrics.
    server.tool(
      "wot_network_health",
      "Get Nostr network health metrics: node count, edge count, Gini coefficient (decentralization), power-law exponent, density, and component analysis. No pubkey needed.",
      {
        payment_hash: z.string().optional().describe("Payment hash if free tier exhausted"),
      },
      async ({ payment_hash }) => {
        const data = await wotGet("/network-health", {}, payment_hash);
        return textResult(formatL402(data));
      }
    );
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses return structure by listing specific metrics, compensating somewhat for missing output schema, but omits rate limits, caching behavior, or freemium authentication details beyond the parameter description.

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 highly efficient sentences with zero waste, front-loaded with verb and resource. Every word earns its place, including the parenthetical list of metrics and the sibling-differentiating final clause.

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?

Adequate for a read-only aggregation tool; compensates for missing output schema by enumerating return metrics and distinguishes from siblings. Could benefit from explicit read-only declaration or rate limiting notes given complete absence of annotations.

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% (payment_hash fully described in schema), establishing baseline 3. The description focuses entirely on output metrics and adds no parameter-specific guidance beyond what the schema provides.

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?

Specific verb 'Get' and resource 'Nostr network health metrics' with exact output enumeration (node count, Gini coefficient, etc.). 'No pubkey needed' explicitly distinguishes this aggregate tool from individual-focused siblings like wot_score or wot_sybil_check.

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?

The phrase 'No pubkey needed' provides clear contextual guidance distinguishing this global network tool from pubkey-specific siblings, though it lacks explicit 'when not to use' statements or named alternative 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/joelklabo/maximumsats-mcp'

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