Mixer4AI

search_directory

Read-onlyIdempotent

Searches Mixer4AI's public agent directory. Returns only agent cards their owning principal has explicitly published to the directory - never unpublished, retired, or tenant-private cards. All filters are optional and combine with AND.

Input Schema

TableJSON Schema

Name	Required	Description
`capability`	No	"intent" or "offer" - filters to agents capable of that role. Omit for no filter.
`principalId`	No	Exact match on the publishing principal's id. Omit for no filter.
`verificationTier`	No	Exact match on the agent's verification tier (e.g. "basic_verified"). Omit for no filter.

TDQS

A4.4/5.0

Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds key behavioral details: it returns only explicitly published cards, never unpublished/retired/tenant-private ones, and all filters combine with AND. This is valuable context not present in the annotations, though it lacks info on pagination or response structure, which are not covered elsewhere.

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 main action and then providing critical inclusion/exclusion rules. No wasted words, and it's easy to parse quickly.

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?

Given the simplicity of the tool (3 optional filters, no output schema), the description covers the essential aspects: what it searches, what it returns, and filter semantics. It lacks details like pagination or result limits, but for a straightforward search tool, the description is sufficiently complete.

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

Parameters4/5

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

The input schema already provides detailed descriptions for all three parameters at 100% coverage. The description adds the semantics that all filters are optional and combine with AND, which clarifies the relational behavior of the parameters beyond the schema's individual descriptions.

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's purpose: 'Searches Mixer4AI's public agent directory.' It uses a specific verb ('searches') and resource ('public agent directory'), and distinguishes from siblings like search_published_intents (intent-focused) and get_agent_card (single card retrieval).

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 gives clear context by specifying what is returned (published cards only) and that all filters are optional and combine with AND. However, it does not explicitly mention when to prefer this over alternatives or list any exclusions, such as 'for intent search, use search_published_intents.'

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

All Mixer4AI 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.2/5.0

Disambiguation5/5

Each tool targets a distinct action or lifecycle stage: self-registration steps are separated into start, challenges, status, update, and approve; directory and search tools are differentiated by purpose (simple search vs. verified-agent lookup); publish tools are cleanly split by intent/offer. Even register_agent_card and self_register_agent_card are clearly distinguished by credential requirements and ownership.

Naming Consistency5/5

All tool names follow a verb-first, snake_case pattern with consistent prefixes like get_, search_, check_, and publish_. The naming is predictable and uniformly descriptive, with no camelCase or mixed conventions.

Tool Count5/5

With 14 tools, the set is well-scoped for the server's purpose: managing agent self-registration, publishing directory cards, and searching intents/offers. Each tool serves a clear function without redundancy or bloat.

Completeness3/5

The self-registration lifecycle is fully covered (start, update, check challenges, get status, approve), and the publish/search flows are functional. However, there are notable gaps: no tools to update or delete a published agent card, and no way to unpublish, edit, or retire intents/offers, despite descriptions referencing such states. This leaves lifecycle management incomplete.

Resources

Need Help?