Agentalog — Agent Auto Log

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: sources says which, and credits 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "a2a_agent_search"
  }
}

Input 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.
`api_pass`	No	MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.
`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 `publisher` 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 changedNov 2, 2026

addedInput schema / properties / api_pass

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

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / publicador / description

Previous value: -"Exact publisher, as `publicador` shows it. Comma-separated values are OR'd (up to 12, each up to 200 characters)."New value: +"Exact publisher, as `publisher` shows it. Comma-separated values are OR'd (up to 12, each up to 200 characters)."

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"
-}

AddedSep 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real substance: no review queue, merge-across-registries behavior, `sources`/`credits` semantics, and a 60s cache. It omits rate limits and whether `api_pass` gates access for this read, which would have completed the picture.

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 the OR/AND rule are reasonably front-loaded, but the middle is bloated with editorializing ('no review queue hides a record; quality is the order, never visibility') and dense run-on sentences. A tighter phrasing would preserve all the operative content in half the length.

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?

With 11 optional params, no output schema, and mutation-free annotations, the key missing piece is what a result row contains — and the description supplies that (key, sources, credits/licenses). Pagination hints live in the schema (`_links.next`). Adequate for correct invocation.

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 coverage is 100%, so baseline is 3; the description earns above that by stating the OR-within/AND-across boolean semantics and the per-row merge semantics that the schema does not express. It does not explain individual params like `skills=1` or `retry_key`, but the schema already does.

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'), defines what an A2A agent is (publishes an AgentCard), and enumerates the filterable dimensions. It is clearly a search/browse tool, distinct from the sibling a2a_agent, which the description implicitly positions as the per-record lookup by referencing the key each row carries.

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?

Provides the crucial combination rule ('values inside one parameter are OR'd, different parameters are AND'd') and routes detail-fetching via 'each row carries the key for a2a_agent'. It also flags a 60-second cache and the forwarding host. It stops short of explicit when-not-to-use guidance against siblings like mcp_index_search or feed_search.

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

All Agentalog — Agent Auto Log tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.