Skip to main content
Glama

wot_compare_providers

Compare trust scores for a Nostr public key across multiple NIP-85 providers to view consensus classification and provider agreement levels.

Instructions

Compare trust scores for a pubkey across multiple NIP-85 providers. Shows consensus classification and provider agreement.

Input Schema

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

Implementation Reference

  • The tool 'wot_compare_providers' is registered and implemented directly in src/index.ts using the server.tool method. It calls the 'wotGet' helper to fetch data from the "/compare-providers" endpoint.
    server.tool(
      "wot_compare_providers",
      "Compare trust scores for a pubkey across multiple NIP-85 providers. Shows consensus classification and provider agreement.",
      {
        pubkey: z.string().describe("Nostr public key in hex format"),
        payment_hash: z.string().optional().describe("Payment hash if free tier exhausted"),
      },
      async ({ pubkey, payment_hash }) => {
        const data = await wotGet("/compare-providers", { pubkey }, payment_hash);
        return textResult(formatL402(data));
      }
    );
Behavior3/5

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

Discloses behavioral output ('consensus classification' and 'provider agreement') but lacks critical operational context given the 'payment_hash' parameter suggests freemium limitations. No mention of rate limits, authentication needs, or what constitutes consensus.

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 with zero waste. Front-loaded with primary action (Compare), followed by output description. Every word earns its place.

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

Completeness3/5

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

Adequate for a read-only comparison tool with rich schema coverage, but missing output structure description (no output schema provided) and NIP-85 domain context that would help agents unfamiliar with Nostr protocols.

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?

With 100% schema coverage, baseline is 3. Description mentions 'pubkey' but adds no semantic detail beyond the schema's 'Nostr public key in hex format'. Baseline maintained.

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?

Specific verb 'Compare' with clear resource 'trust scores' and scope 'across multiple NIP-85 providers'. Implicitly distinguishes from sibling 'wot_score' (single score) by emphasizing cross-provider comparison and consensus.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this versus siblings like 'wot_score' or 'wot_sybil_check'. While 'across multiple providers' implies use-case, there are no 'when to use' or 'when not to use' directives.

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