Skip to main content
Glama

wot_trust_circle

Analyze a Nostr user's trust network by retrieving mutual follows with trust strength metrics, including member roles, cohesion, and density data for reputation assessment.

Instructions

Get a pubkey's trust circle (mutual follows with trust strength). Returns members with roles, cohesion, and density metrics.

Input Schema

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

Implementation Reference

  • The handler function for the wot_trust_circle tool, which fetches data from the /trust-circle endpoint.
    async ({ pubkey, payment_hash }) => {
      const data = await wotGet("/trust-circle", { pubkey }, payment_hash);
      return textResult(formatL402(data));
    }
  • src/index.ts:189-200 (registration)
    Registration of the wot_trust_circle tool with the MCP server, including its description and input schema.
    server.tool(
      "wot_trust_circle",
      "Get a pubkey's trust circle (mutual follows with trust strength). Returns members with roles, cohesion, and density metrics.",
      {
        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("/trust-circle", { pubkey }, payment_hash);
        return textResult(formatL402(data));
      }
    );
Behavior4/5

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

With no annotations or output schema, the description carries the full burden: it discloses the output structure ('Returns members with roles, cohesion, and density metrics') and implicitly reveals payment behavior by referencing the payment_hash parameter's purpose for when 'free tier [is] exhausted'.

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 tightly constructed sentences with zero waste: the first establishes operation and scope, while the second describes output structure, making it appropriately front-loaded and concise.

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 the absence of annotations and output schema, the description adequately compensates by detailing return values (members, roles, cohesion, density metrics) and payment behavior, though explicitly noting the read-only nature would provide additional context.

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?

With 100% schema description coverage (baseline 3), the description adds value beyond the schema by contextualizing the pubkey as the target of the trust circle analysis and clarifying the payment_hash's role in tier management.

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?

The phrase 'Get a pubkey's trust circle' provides a specific verb and resource, while the parenthetical '(mutual follows with trust strength)' distinguishes this tool from siblings like wot_follow_quality or wot_trust_path by defining the specific trust mechanics involved.

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?

While it lacks explicit 'when-to-use' directives against alternatives, the parenthetical clarification '(mutual follows with trust strength)' provides implied usage context that distinguishes it from path-finding or follow-quality analysis, though explicit guidance would be stronger.

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