meta-agent-tools

A2a agent search

a2a_agent_search

Read-onlyIdempotent

Find A2A agents — agents that publish an AgentCard — by text, health, protocol version, registry, skill tag or publisher. Each row carries the key for a2a_agent and the license of every registry that lists it. Collected from public A2A registries and served as it comes — no review queue hides a record; quality is the order, never visibility. One row per agent, merged across the registries that list it: fontes says which, and creditos carries each one's license, which travels with the data. Values inside one parameter are OR'd, different parameters are AND'd. Cached for 60 seconds. A MAT catalog read, served by the index host https://api.agentalog.com; this host forwards the call there.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Substring of the name, description, key, publisher or the card's skills, in any letter case (`%` and `_` are taken literally); up to 80 characters.
`tag`	No	Exact tag of the card's skills, case-sensitive; `/api/a2a/facets` lists the 40 most used. Comma-separated values are OR'd (up to 12, each up to 200 characters).
`fonte`	No	Only agents listed by this registry. Comma-separated values are OR'd (up to 12, each up to 200 characters).
`limit`	No	Items per page, 1–50; more is capped at 50, anything else means 20.
`saude`	No	Health the registries measured: `sim` answered, `nao` did not, `sem_medida` never measured. Comma-separated values are OR'd (up to 12, each up to 200 characters).
`offset`	No	Offset, capped at 20000 (a larger value reads as 20000). Prefer `_links.next`.
`skills`	No	`1` keeps only agents whose card lists at least one skill.
`protocolo`	No	A2A protocol version as normalized (`0.3`, `1.0`…); `/api/a2a/facets` lists the ones present. Comma-separated values are OR'd (up to 12, each up to 200 characters).
`retry_key`	No	Optional retry key, up to 80 ASCII characters; same read for five minutes.
`publicador`	No	Exact publisher, as `publicador` shows it. Comma-separated values are OR'd (up to 12, each up to 200 characters).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

removedInput schema / properties / api_pass

Removed value: -{
-  "description": "MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.",
-  "type": "string"
-}

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / q / description

Previous value: -"Substring of the name, description, key, publisher or the card's skills — case-sensitive; up to 80 characters."New value: +"Substring of the name, description, key, publisher or the card's skills, in any letter case (`%` and `_` are taken literally); up to 80 characters."

AddedSep 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations cover only the safety profile (readOnly/idempotent/non-destructive), while the description adds substantial behavioral context the annotations cannot: 60-second caching, no review queue, one row per agent merged across registries, the `fontes`/`creditos` provenance fields, and the fact that the call is forwarded to `https://api.agentalog.com`. This is exactly the extra context the lower bar for annotated tools rewards.

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?

Purpose and filters are front-loaded, but the sentence 'no review queue hides a record; quality is the order, never visibility' is promotional filler that does not help an agent invoke the tool. The hosting/forwarding sentence is useful but the prose is longer than the actionable content requires.

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?

For a 10-parameter tool with no output schema, the description supplies merge semantics, provenance fields, boolean logic, and caching. Return-shape detail is thin (only that rows carry a key and license), and pagination is delegated to the schema's `_links.next`, leaving minor gaps.

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?

Schema description coverage is 100%, so the baseline is 3. The description goes beyond it by stating the cross-parameter logic — 'Values inside one parameter are OR'd, different parameters are AND'd' — which the per-parameter schema descriptions do not spell out.

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 and resource ('Find A2A agents') and immediately defines the entity ('agents that publish an AgentCard') plus the full set of filter dimensions. It also distinguishes itself from the sibling a2a_agent by noting each row 'carries the key for a2a_agent', making the search-vs-fetch split clear without opening either schema.

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?

Routing cues are present: rows carry the key for a2a_agent, and `/api/a2a/facets` is named as the place to enumerate tag and protocol values. It does not state explicit when-not-to-use conditions or an alternative search tool, so it stops short of full 5-level guidance.

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

All meta-agent-tools tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?