Skip to main content
Glama

wot_trust_path

Discover how two Nostr users are connected by analyzing trust relationships between their public keys, displaying the path and trust scores at each hop.

Instructions

Find the trust path between two Nostr pubkeys. Shows hop-by-hop path with trust scores at each hop. Useful for 'how am I connected to this person?'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesSource Nostr pubkey in hex
toYesTarget Nostr pubkey in hex
payment_hashNoPayment hash if free tier exhausted

Implementation Reference

  • The registration and handler implementation for the `wot_trust_path` tool. It takes `from` and `to` pubkeys, calls the `wotGet` helper, and formats the result.
    server.tool(
      "wot_trust_path",
      "Find the trust path between two Nostr pubkeys. Shows hop-by-hop path with trust scores at each hop. Useful for 'how am I connected to this person?'",
      {
        from: z.string().describe("Source Nostr pubkey in hex"),
        to: z.string().describe("Target Nostr pubkey in hex"),
        payment_hash: z.string().optional().describe("Payment hash if free tier exhausted"),
      },
      async ({ from, to, payment_hash }) => {
        const data = await wotGet("/trust-path", { from, to }, payment_hash);
        return textResult(formatL402(data));
      }
    );
Behavior3/5

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

Discloses output format (hop-by-hop with trust scores) which compensates for missing output schema. However, lacks disclosure of free tier constraints (only mentioned in schema parameter), error behavior when no path exists, or side effects. No annotations provided to contradict.

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?

Three sentences each earning their place: (1) core action, (2) output format, (3) use case. No redundancy or boilerplate. Perfectly front-loaded with action verb.

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?

Given no output schema, description adequately describes return structure (hop-by-hop with scores). All 3 parameters documented (100% schema coverage). Minor gap: doesn't explain 'no path found' behavior or free tier limits beyond schema parameter hint.

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 has 100% coverage with clear descriptions ('Source Nostr pubkey', 'Target Nostr pubkey'). Description mentions 'two Nostr pubkeys' aligning with required params, but adds no syntax/format details beyond well-documented schema. Baseline 3 appropriate for high-coverage 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 'Find' + resource 'trust path' + domain 'Nostr pubkeys' clearly establishes scope. Distinguishes from siblings like wot_score (returns aggregate score) and wot_trust_circle (returns clusters) by specifying 'path between two' pubkeys.

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?

Clear use case provided: answering 'how am I connected to this person?' Guides agent toward path-discovery queries between specific entities. Missing explicit alternatives (e.g., 'use wot_score for single-user ratings') but provides strong positive guidance.

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