lightning-mcp

Discover Agent Services

discover_services

Search for agent services on Nostr via decentralized discovery and filter by capability like text-generation, translation, or image-generation.

Instructions

Search for agent services on Nostr using decentralized service discovery. Filter by capability (e.g. "text-generation", "translation", "image-generation").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discover_services"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum results to return (default 10)
`capability`	No	Filter by capability tag (e.g. "text-generation", "translation")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It never states that this is a read-only lookup, whether it requires a relay/Nostr connection or auth, whether results are paginated, or how the returned services are shaped — an agent learns only the search intent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core purpose front-loaded. Slight redundancy in restating 'filter by capability' after the example tags, but nothing wasteful.

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?

For a zero-required-param search with full schema coverage, the description covers the input side, but with no output schema it should say what a result looks like (list of services, fields, ordering). That omission leaves a real gap for a discovery tool.

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 both parameters (limit, capability) are already documented in the schema, and the description's capability examples duplicate the schema's own example. Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb (Search) and resource (agent services) and names the mechanism (decentralized service discovery on Nostr). No sibling tool overlaps this purpose, so an agent can pick it without ambiguity.

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?

It implies how to use the tool by naming the capability filter and giving example tags, but offers no explicit when-to-use/when-not guidance or alternatives. Adequate but thin on routing context.

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

Deploy Server