Skip to main content
Glama

wot_follow_quality

Analyze Nostr pubkey follow lists to assess quality, identify ghost followers, measure diversity, and provide improvement suggestions for better network connections.

Instructions

Analyze the quality of a Nostr pubkey's follow list. Returns quality score, ghost follower ratio, diversity entropy, and improvement suggestions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pubkeyYesNostr public key in hex format
payment_hashNoPayment hash if free tier exhausted

Implementation Reference

  • Handler function for wot_follow_quality tool which calls the /follow-quality endpoint.
    async ({ pubkey, payment_hash }) => {
      const data = await wotGet("/follow-quality", { pubkey }, payment_hash);
      return textResult(formatL402(data));
    }
  • Input schema definition for wot_follow_quality tool.
    {
      pubkey: z.string().describe("Nostr public key in hex format"),
      payment_hash: z.string().optional().describe("Payment hash if free tier exhausted"),
    },
  • src/index.ts:176-178 (registration)
    Tool registration for wot_follow_quality.
    server.tool(
      "wot_follow_quality",
      "Analyze the quality of a Nostr pubkey's follow list. Returns quality score, ghost follower ratio, diversity entropy, and improvement suggestions.",
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. Lists specific return values (quality score, ghost follower ratio, diversity entropy, suggestions) which helps understand output behavior. However, omits operational details: rate limits, cost implications of 'free tier,' or whether analysis is cached/real-time.

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 efficient sentences with zero waste. Front-loaded with action verb, follows with return value documentation. Every word earns its place.

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?

Good coverage given no output schema: enumerates four specific return metrics (quality score, ghost follower ratio, diversity entropy, suggestions). Would benefit from brief explanation of 'ghost follower' concept or payment model details, but adequately complete for tool selection.

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% with clear descriptions ('Nostr public key in hex format', 'Payment hash if free tier exhausted'). Description adds functional context about analyzing follow lists but doesn't supplement parameter syntax or validation rules beyond schema.

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 'Analyze' + resource 'Nostr pubkey's follow list' + scope 'quality'. Clearly distinguishes from siblings like wot_score (general scoring), wot_sybil_check (sybil detection), and wot_influence (influence metrics) by focusing specifically on follow list quality.

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?

Implies usage through specificity ('follow list quality' vs other WoT metrics), but lacks explicit guidance on when to choose this over wot_score or wot_anomalies. No mention of prerequisites or conditions beyond the payment_hash hint.

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