Skip to main content
Glama

Find mcp or api

find_mcp_or_api

Which MCP server or API does this? Matches from the official MCP registry (37,000+ servers) and the APIs.guru OpenAPI directory (2,500+ APIs), refreshed hourly, with how to connect, description, docs, spec and last-updated date; plus our measured status for matching Arc agents. Listed is not working: we do not test these. A search with no match is refused before payment. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
qYeswhat tool or API you need, in plain words
kindNoany (default), mcp or api
limitNoresults, 1-20 (default 10)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses data sources, hourly refresh, the exact return fields, the non-verified caveat ('Listed is not working: we do not test these'), the pre-payment refusal on no match, and a concrete price plus payment rails. Missing only operational details such as rate limits or latency.

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?

Front-loaded with the core question and sources, then freshness, caveats, pricing and the payment flow in a logical order with no filler sentences. Dense but every clause carries information; the payment mechanics run slightly long for a discovery tool.

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?

No output schema and no annotations, yet the description enumerates the fields returned (connection info, description, docs, spec, last-updated) and covers cost, freshness and call sequencing. An agent has enough to invoke it correctly, though the literal response shape is not spelled out.

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 q, kind, limit and payment are already fully documented in the schema, including the PAYMENT-SIGNATURE payload format. The description adds the two-call payment workflow but no new syntax or constraints for the individual parameters, so the baseline of 3 applies.

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?

Opens with a specific verb-and-resource question ('Which MCP server or API does this?') and names exactly which corpora it searches (official MCP registry, APIs.guru OpenAPI directory). An agent can distinguish it from sibling catalogs like catalog_browse or market_search without opening the schema.

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?

Gives clear invocation context: search with no match is refused before payment, and the x402 flow is 'call once without payment for the terms, sign them, call again with payment.' It also sets expectations that listings are not tested. It does not compare itself to sibling discovery tools, so no explicit alternatives guidance.

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