Skip to main content
Glama
Sign In

Agentry — The Trust Layer for the Agent Economy

by io.github.cthulhutoo
OverviewDiscussionsAdmin

a2a_public_discovery_api_agents_public_get

A2A Public Discovery

A2A-compatible open discovery endpoint.

Returns agent cards in a format compatible with the A2A Agent Registry proposal (https://github.com/a2aproject/A2A/discussions/741).

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch query to filter agents
topNo
cursorNoPagination cursor
categoryNoFilter by category

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the burden of disclosure. It mentions the response format (agent cards, A2A-compatible) and a 200 response with content-type, but does not state read-only semantics, pagination behavior, error handling, or any side effects. The absence of a readOnlyHint makes this a notable gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the title and key purpose. The 'Responses' section is minimal but not overly verbose. It avoids unnecessary fluff, though it could be better structured with more meaningful response details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 optional parameters, no output schema, and no annotations, the description is incomplete. It does not explain how to use pagination (top, cursor) or filtering (q, category), nor does it describe the agent card structure or any error conditions, leaving a substantial gap for an agent to correctly invoke the tool.

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

Parameters2/5

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

Schema description coverage is 75% (q, cursor, category are described, top is not). The description adds no parameter-level meaning, failing to compensate for the undocumented 'top' parameter or explain how q, category, and cursor interact. It adds no value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns agent cards in an A2A-compatible format, using the verb 'returns' with a specific resource. It does not explicitly differentiate from sibling tools like list_agents or search_agents, but the A2A compatibility and 'open discovery endpoint' provide some distinguishing context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or comparison to sibling tools such as discover_single_agent or list_agents, leaving the agent without decision support.

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

All Agentry — The Trust Layer for the Agent Economy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources