Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

by io.github.AgentTools-Cloud

register

Self-register an x402 / MCP service in the agent-tools directory.

Service owners and agents may submit new services here. Submissions
are auto-reviewed instantly by x402 verification (no human gate): if
the URL proves x402 payment support it is listed immediately and shows
up in `search`; otherwise it is rejected or retried automatically.
Listing is FREE.

Dedup: if a service with the same canonical origin (scheme://host)
already exists in the directory we return its slug instead of
creating a duplicate submission. Same goes for a still-pending
submission with the same origin.

Rate limit: at most 5 pending submissions per client IP per 24h.
Hits beyond that get `{error: rate_limited}` — try again later or
email contact@agent-tools.cloud for bulk imports.

Args:
    url: Public HTTPS URL of the service (the x402-payable endpoint
        or its homepage). Required.
    name: Human-friendly name. Defaults to the URL hostname.
    description: One-paragraph description (max ~2000 chars).
    mcp_url: If the service speaks MCP, its streamable-http endpoint.
    category: Free-form (e.g. "defi", "search", "social"). Use
        `list_categories` to align with existing taxonomy.
    chains: Networks the service accepts payment on
        (e.g. ["base", "solana"]).
    price_min_usdc: Lower bound of per-call price in USDC.
    price_max_usdc: Upper bound of per-call price in USDC.
    contact: Optional email / handle the directory team can reach
        you on for clarifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
nameNo
chainsNo
contactNo
mcp_urlNo
categoryNo
descriptionNo
price_max_usdcNo
price_min_usdcNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A5/5.0
Behavior5/5

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

Since no annotations provided, description fully discloses behavior: auto-review via x402 verification, immediate listing or retry, dedup, rate limiting with specific error message, and contact for bulk imports. No contradictions.

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?

Well-structured with clear sections: purpose, process, dedup, rate limit, then args. Concise yet comprehensive; every sentence adds value.

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 9 parameters, no annotations, and output schema available, description covers all behavioral aspects: error conditions, dedup, rate limit, and parameter semantics. No need to explain output since schema exists.

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%, but description adds meaning for all 9 parameters: url required, name defaults to hostname, description max chars, category suggests list_categories, chains, price bounds, contact optional. Fully compensates for schema gaps.

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 registers an x402/MCP service in the agent-tools directory. It distinguishes from sibling tools like search and list_categories by explicitly mentioning the registration purpose and auto-review process.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use (service owners/agents submitting new services), dedup logic (avoids duplicates), rate limit (5 per IP per 24h), and alternatives (search for existing listings). Also describes error handling for rate limits.

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