Skip to main content
Glama

Lordevo Agent Directory

List verified x402 services

list_verified
Read-only

x402 pay-per-call endpoints whose live unpaid HTTP 402 quote equals the listed price, with latency and last check time. Cheapest first by default. Read-only; Lordevo checks without paying.

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": "list_verified"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional keywords
sortNo
limitNo
categoryNo
max_priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds real value beyond that by disclosing that checks are performed without paying ('Lordevo checks without paying'), plus the default sort and the returned latency/last-check fields. It omits pagination behavior, rate limits, and how stale a failed verification becomes.

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?

Three short, dense sentences with the defining criterion front-loaded and no filler. The telegraphic noun-phrase opening slightly reduces readability, but nothing is wasted.

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

Completeness2/5

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

With five optional filters at 20% schema coverage and no output schema, the description should have carried the filter semantics and the shape of results. It instead covers only the verification criterion and default ordering, leaving four parameters undefined anywhere in the definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% — only q ('Optional keywords') is documented, while sort, limit, category, and max_price carry no meaning in structured data. The description compensates only partially: 'Cheapest first by default' implies sort=price default and 'latency' names one enum value, but max_price, category, and limit bounds (1–50) remain unexplained.

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 states the resource precisely: x402 pay-per-call endpoints whose live unpaid 402 quote matches the listed price, plus latency and last-check metadata. The verb is implied rather than stated (a noun-phrase fragment), and it never names how it differs from sibling search_services, but an agent can still tell this returns price-verified endpoints.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no reference to search_services, list_categories, or get_service. 'Cheapest first by default' hints at ordering but not at tool selection, so the agent must infer that 'verified' means this is the trustworthy-price variant of a search.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources