Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

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.

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": {
      "url": "<url>"
    },
    "name": "register"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS URL of the service (the x402-payable endpoint or its homepage). Required.
nameNoHuman-friendly name. Defaults to the URL hostname.
chainsNoNetworks the service accepts payment on (e.g. ["base", "solana"]).
contactNoOptional email / handle the directory team can reach you on for clarifications.
mcp_urlNoIf the service speaks MCP, its streamable-http endpoint.
categoryNoFree-form (e.g. "defi", "search", "social"). Use `list_categories` to align with existing taxonomy.
descriptionNoOne-paragraph description (max ~2000 chars).
price_max_usdcNoUpper bound of per-call price in USDC.
price_min_usdcNoLower bound of per-call price in USDC.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes far beyond the annotations: discloses the instant no-human x402 review gate, what happens on pass vs. fail, that listing is free, the exact dedup rule (canonical scheme://host → returns existing slug, including pending submissions), and a concrete rate limit of 5 pending submissions per IP per 24h with the exact error shape and a bulk-import escalation path.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The behavioral preamble is well front-loaded and earns its space, but the 'Args:' section duplicates a schema that is already 100% documented, consuming roughly a third of the text with zero marginal information.

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?

For a 9-parameter mutation tool with an output schema, the description covers everything an agent needs to act correctly: submission path, review outcome, dedup semantics, and rate-limit failure handling with a recovery route. Return values are correctly left to the output schema.

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 already 100%, and the 'Args:' block restates each parameter's schema description nearly verbatim, adding no new semantics. The one value-add — 'Use `list_categories` to align with existing taxonomy' — is also present in the schema. Baseline 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+resource+scope: 'Self-register an x402 / MCP service in the agent-tools directory.' Clearly distinct from every sibling (search, get, list_categories, stats), so an agent knows this is the only creation path.

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?

Explicitly states who should use it ('Service owners and agents may submit new services here') and routes the agent to `list_categories` for taxonomy alignment. It doesn't cover when NOT to register (e.g., how to update an existing mis-listed service vs. re-registering), which keeps it below a 5.

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.