Skip to main content
Glama

Agentalog — Agent Auto Log

by com.agentalog
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSubstring of the name, description, key, publisher or the card's skills, in any letter case (`%` and `_` are taken literally); up to 80 characters.
tagNoExact 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).
fonteNoOnly agents listed by this registry. Comma-separated values are OR'd (up to 12, each up to 200 characters).
limitNoItems per page, 1–50; more is capped at 50, anything else means 20.
saudeNoHealth 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).
offsetNoOffset, capped at 20000 (a larger value reads as 20000). Prefer `_links.next`.
skillsNo`1` keeps only agents whose card lists at least one skill.
protocoloNoA2A 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_keyNoOptional retry key, up to 80 ASCII characters; same read for five minutes.
publicadorNoExact 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.

  1. Changed1 schema field changed
    • 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)."
  2. Changed1 schema field changed
    • 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"
-}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

With readOnly/idempotent/non-destructive already declared by annotations, the description still adds real behavior: 60-second caching, retry_key dedup window, provenance from public registries with no review queue, one merged row per agent with `sources` and `credits` licenses, and that the call is forwarded to `https://api.agentalog.com`. It does not describe rate limits or error behavior, keeping it below a 5.

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 purpose is front-loaded, but the marketing flourish ('served as it comes — no review queue hides a record; quality is the order, never visibility') and the host-forwarding sentence consume space without helping the agent select or call the tool. Useful content and flavor text are interleaved rather than cleanly separated.

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, no-required, no-output-schema search tool, the description covers return shape (one row per agent, sources, credits, key for a2a_agent), merge semantics and pagination pointers, which is what an agent needs to act. Only minor gaps remain, such as ordering of results.

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 the parameter baseline is 3; the description goes beyond it by stating the cross-parameter combination rule ('Values inside one parameter are OR'd, different parameters are AND'd'), which the schema does not express, plus the shape of each returned row.

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?

States a specific verb (find) and resource (A2A agents, defined as agents publishing an AgentCard) plus the filter axes it accepts. It also distinguishes itself from the sibling a2a_agent by noting 'Each row carries the key for a2a_agent', so an agent understands this is the search step of a two-step flow 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?

Gives practical invocation context: query tag/publisher/protocol values via `/api/a2a/facets`, and 'Prefer `_links.next`' for pagination; the OR-within / AND-across rule tells the agent how to combine filters. It never states when NOT to use it versus a sibling like a2a_agent, so it stops short of full when/when-not guidance.

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 toolsInspect
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