Skip to main content
Glama

Lordevo Agent Directory

Search the Lordevo Agent Directory

search_services
Read-only

Find APIs, x402 pay-per-call endpoints (USDC on Base) and MCP servers by keyword. Returns endpoint, price, payment method, auth and docs for each result. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWhat you need, in plain words
kindNo
sortNorelevance (default), price = cheapest first, latency = fastest first
limitNo
paymentNo
categoryNo
verifiedNoOnly x402 listings whose live 402 quote equals the listed price
max_priceNoMax USD per call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "relevance (default), price = cheapest first, latency = fastest first",
      +  "enum": [
      +    "relevance",
      +    "price",
      +    "latency"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / verified
      Added value: +{
      +  "description": "Only x402 listings whose live 402 quote equals the listed price",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so 'Read-only.' adds nothing and duplicates structured data. The description does add real value by disclosing the shape of each result (endpoint, price, payment method, auth, docs) and the x402/USDC-on-Base payment context, but it omits ranking behavior, result caps, and what a live 402 quote means.

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, front-loaded with what is searchable and followed by what comes back. The trailing 'Read-only.' fragment is redundant with the annotations and is the only wasted element.

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 an eight-parameter search tool this covers the core idea and compensates somewhat for the missing output schema by describing returned fields. However, it leaves the agent guessing about filtering dimensions, price units, and how sort/verified interact, which matters given the parameter count.

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?

With only 50% schema description coverage and 8 parameters, four parameters (kind, limit, payment, category) carry no explanation in either the schema or the description. The description mentions price and payment method only as return fields, not as filterable inputs, so it does not compensate for the coverage gap.

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 uses a specific verb ('Find') plus an enumerated resource set (APIs, x402 pay-per-call endpoints, MCP servers) and names the matching mechanism ('by keyword'). It does not explicitly distinguish itself from siblings like list_categories or list_verified, so it stops short of a 5.

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?

Usage is only implied: 'by keyword' signals a free-text search rather than a browse/list operation. There is no explicit when-to-use or when-not-to-use guidance and no pointer to get_service or list_verified for lookup-by-id or filtered browsing.

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