Agent Arena Registry

search_agents

Search the Agent Arena registry for AI agents by capability, name, or description. Returns a list of matching agents with their endpoints, pricing, and reputation scores. Requires $0.005 USDC payment via x402 on Base mainnet.

Input Schema

TableJSON Schema

Name	Required	Description
`acta`	No	Only return agents with ACTA-ready private credential metadata
`oasf`	No	Only return agents with a hosted OASF Agent Directory record
`chain`	No	Filter by chain name, e.g. 'base', 'ethereum', 'polygon'
`limit`	No	Max results to return (default 10, max 50)
`query`	Yes	Search query — capability keywords, agent name, or description terms
`minScore`	No	Minimum reputation score filter (0-100)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJun 15, 2026

addedInput schema / properties / oasf

Added value: +{
+  "description": "Only return agents with a hosted OASF Agent Directory record",
+  "type": "boolean"
+}

Changed1 schema field changedMay 25, 2026

addedInput schema / properties / acta

Added value: +{
+  "description": "Only return agents with ACTA-ready private credential metadata",
+  "type": "boolean"
+}

First observedFeb 23, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description bears the burden of transparency. It discloses the $0.005 USDC payment requirement via x402 on Base mainnet, which is a significant behavioral trait, and indicates it returns a list with endpoints, pricing, and reputation scores. However, it does not explicitly state whether the operation is read-only or what happens on payment failure.

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 two concise sentences, front-loaded with the action and resource, and includes key behavioral context without unnecessary verbosity.

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?

The description covers the tool's purpose, return data, and payment requirement. Given the schema fully documents parameters and there is no output schema, the description is largely complete for an agent to decide when and how to use the tool. It lacks explicit comparison to siblings but that is handled in usage guidelines.

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 descriptions cover 100% of parameters, so the baseline is 3. The description adds minimal additional semantics beyond what the schema provides, such as indicating the query searches by capability, name, or description, but it does not elaborate on individual parameters.

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 searches the Agent Arena registry for AI agents by capability, name, or description, distinguishing it from sibling tools get_agent_profile and register_agent.

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?

The description implies usage for discovering agents but does not explicitly contrast with get_agent_profile or register_agent, or state when not to use it. The context is clear but exclusions and alternatives are not stated.

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

All Agent Arena Registry tools Inspect

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

A4.3/5.0

Disambiguation5/5

Each tool targets a distinct operation: retrieving a specific agent profile, registering a new agent, and searching the registry. There is no overlap in purpose, making selection unambiguous.

Naming Consistency5/5

All tools follow the verb_noun pattern: get_agent_profile, register_agent, search_agents. The naming is uniformly descriptive and predictable.

Tool Count5/5

Three tools is well-scoped for a registry that offers core create, read, and search functionality. Each tool serves a clear, non-redundant purpose.

Completeness4/5

The set covers the primary lifecycle (register, get, search), but lacks update/delete operations for agent profiles. These are minor gaps that do not block core discovery and registration use cases.

Resources

Need Help?