Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

by io.github.AgentTools-Cloud

search

Find x402 / MCP services matching an intent or filter set.

Two usage modes (agents pick whichever fits):
  A. Natural-language: `search(intent="fetch tweets for @user")`
  B. Pure browse:      `search(has_mcp=True, category="defi", top_k=10)`
     At least one of `intent`, `category`, `chain`, `has_mcp`,
     `min_confidence` must be supplied — otherwise the call is
     rejected (we won't dump 2300+ rows).

Results are ranked by:
    (health=ok AND tx_30d>0) → health=ok → has-quality-signal →
    confidence → tx_30d → recency.
So the highest-quality real-traffic services appear first.

Each item includes (when available):
  - confidence    : 0.0–1.0 x402scan quality score.
  - tx_30d        : 30-day x402 payment count (proxy for real usage).
  - match_snippet : FTS snippet showing where `intent` hit ([[token]]).
  - match_reason  : list[str] of human-readable ranking signals.
  - mcp_url       : populated when the service exposes an MCP endpoint
                    (you can call it directly via streamable-http).
Agents should prefer items with non-null confidence and tx_30d > 0
unless the user explicitly wants experimental endpoints.

Args:
    intent: What the agent wants to do (English or Chinese). Optional
        when at least one structured filter is set. Synonym expansion
        covers twitter↔X↔推特, whale↔巨鲸, price↔价格 etc.
    top_k: Max services to return (default 5, hard cap 25).
    max_price_usd: Upper bound on per-call price in USD.
    category: Filter (see `list_categories`).
    chain: "base", "polygon", "solana", "arbitrum", ...
    min_confidence: Minimum confidence (0.0–1.0). 0.8+ keeps only
        services x402scan rates as high-quality.
    has_mcp: When true, return only services with a callable MCP
        endpoint. Use this when the agent wants to chain another MCP
        server rather than perform raw HTTP+x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNo
top_kNo
intentNo
has_mcpNo
categoryNo
max_price_usdNo
min_confidenceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries full burden. It discloses the ranking logic (health, tx_30d, etc.), the fact that the call is rejected without filters, and recommends preferring items with non-null confidence and tx_30d > 0. This provides clear behavioral expectations beyond the schema.

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?

The description is well-structured with sections, bullet points, and clear formatting. It is comprehensive but every sentence adds value. No filler or repetition. The use of examples and formatting makes it easy to parse quickly.

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

Completeness5/5

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

Given the complexity (7 parameters, output schema exists), the description thoroughly explains ranking, result fields, and parameter semantics. The output schema exists but description also clarifies the content of results like confidence, tx_30d, match_snippet, etc., making it fully complete for an agent to use.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must fully compensate. It provides detailed explanations for each of the 7 parameters in a dedicated Args section, including examples for intent, default values, and constraints like hard cap for top_k. This adds significant meaning beyond the raw schema.

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?

The description clearly states the tool finds x402/MCP services matching an intent or filter set. It specifies two usage modes (natural-language and pure browse) and distinguishes from sibling tools by mentioning specific filtering capabilities and contrast with other search tools.

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 description provides explicit when-to-use guidance by detailing two usage modes and mandatory filter requirements. It explains that at least one filter must be supplied to avoid rejection. However, it does not explicitly compare with siblings like 'search_mcp_servers' to indicate when to use one over the other.

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

All agent-tools (x402 + MCP + A2A directory) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Tools are mostly distinct with clear purposes. However, 'search', 'search_mcp_servers', 'search_a2a_agents', 'search_resources', and 'ask_services' have overlapping discovery functions, though descriptions differentiate them (e.g., LLM ranking vs deterministic). This could slightly confuse an agent.

Naming Consistency3/5

Naming conventions are mixed: some follow 'verb_noun' (e.g., ask_services, list_categories), some are single verbs (get, register, search, stats), and some use underscores (search_a2a_agents, search_mcp_servers). The pattern is not fully consistent but remains readable.

Tool Count5/5

11 tools is well within the recommended 3-15 range for a directory server covering x402, MCP, and A2A services. Each tool serves a distinct purpose without bloat.

Completeness4/5

The toolset covers core directory operations: discovery (multiple search variants), details, registration, safety scanning, and stats. Missing update/delete for services is a minor gap but not critical for basic usage.

Resources