Skip to main content
Glama
forgesworn

402-mcp

by forgesworn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

l402-search

Read-only

Discover paid APIs by searching Nostr relays for kind 31402 announcements, returning URLs, pricing, and capabilities. Filter by topic, payment method, or query text.

Instructions

Search Nostr relays for paid API announcements (kind 31402) and return their URLs, pricing and capabilities. Topic filters are sent to the relays; the payment method and query text are matched locally. Announcement text is written by whoever published it and is marked as untrusted content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query to match against service names, descriptions, and capabilities
relaysNoNostr relay URLs to query (defaults to popular public relays)
topicsNoFilter by topic tags (e.g. ["ai", "data"])
timeoutNoRelay subscription timeout in milliseconds (default 5000)
maxResultsNoMaximum number of results to return (default 20)
paymentMethodNoFilter by payment rail, the first value of an announcement's pmi tag (e.g. "l402", "cashu", "xcashu", "lnurlcash", "x402", "payment"). A Cashu service may list "cashu", "xcashu" or both

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.3.1
    • changedInput schema / properties / paymentMethod / description
      Previous value: -"Filter by payment method (e.g. \"l402\", \"cashu\", \"x402\", \"xcashu\")"New value: +"Filter by payment rail, the first value of an announcement's pmi tag (e.g. \"l402\", \"cashu\", \"xcashu\", \"lnurlcash\", \"x402\", \"payment\"). A Cashu service may list \"cashu\", \"xcashu\" or both"
  2. First observedv4.2.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark the tool as read-only and open-world, and the description adds genuinely useful behavioral details: topic filters are sent to relays while payment/query matching happens locally, and announcement text is untrusted. It does not cover pagination or output shape, but for a read-only search tool this is sufficient.

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 focused sentences: the first front-loads the action and result, the second clarifies the filtering behavior, and the third warns about content trustworthiness. No sentence is wasted.

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?

With no output schema, the description still names the high-level return values and the kind of content searched, and the input schema covers all six parameters. It could be slightly more explicit about result limits or failure behavior, but it gives an agent enough to call the tool correctly.

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 description coverage is 100%, so the parameters are already well documented. The description adds slight context about where query and payment-method filtering occurs, but it does not materially extend the parameter semantics beyond the schema.

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?

The description opens with a specific verb and resource: 'Search Nostr relays for paid API announcements (kind 31402)', and it lists the returned information (URLs, pricing, capabilities). It is clear about what the tool does, though it does not explicitly differentiate itself from siblings like l402-discover or l402-service-directory.

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 first sentence gives clear context for when to use this tool: when an agent needs to discover paid API announcements published on Nostr relays. It does not provide exclusions or direct alternatives, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools