Skip to main content
Glama

Agentry — The Trust Layer for the Agent Economy

by io.github.cthulhutoo

list_agents_api_agents_get

List Agents

List AI agents in the Agentry directory with optional filtering and pagination.

Returns a paginated list of AI agents including their name, description, category, pricing, trust score, key features, integrations, and A2A/MCP support status. The directory contains 122+ agents across 11 categories.

Responses:

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of agents to return per page. Range: 1-100.
offsetNoNumber of agents to skip for pagination. Use with limit for paging.
categoryNoFilter agents by category name (e.g. 'Sales & Outreach', 'Customer Support', 'Development Tools'). Returns all categories if omitted.

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions the return is a paginated list and enumerates the fields included, but doesn't disclose authentication requirements, rate limits, or sorting behavior. This is sufficient for a simple read-only list, but not particularly rich.

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 mostly concise and front-loaded with the purpose, but includes a redundant header 'List Agents' and a nearly empty 'Responses' section that only states '200: Successful Response' and content type. This is minor waste but not a major issue.

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?

The description gives a good overview of returned fields and directory size, which helps an agent understand the tool's output without an output schema. It doesn't explain pagination mechanics or error cases, but for a straightforward listing tool with clear schema parameters, it is reasonably complete.

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

Parameters3/5

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

Schema coverage is 100%, and the description only mentions 'optional filtering and pagination' without adding details beyond the schema. The schema already documents limit, offset, and category with examples, so the description adds minimal additional meaning.

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 lists AI agents in the Agentry directory, which is a specific verb+resource. The inclusion of 'with optional filtering and pagination' further clarifies scope. It distinguishes from siblings like search_agents and get_agent by focusing on listing rather than searching or retrieving a single agent.

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

Usage Guidelines3/5

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

The description implies the tool is for browsing the agent directory with optional filtering and pagination, but does not explicitly state when to use it over alternatives like search_agents or list_categories. No exclusions or alternative tool recommendations are provided.

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

B3.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with descriptions that differentiate related operations like discovery vs. scanning or mint vs. melt quotes. A few pairs (e.g., list_agents vs. a2a_public_discovery, get_agent vs. discover_single_agent) could cause confusion, but the endpoint paths and descriptions mitigate this.

Naming Consistency5/5

All tool names follow a consistent pattern: a descriptive operation prefix followed by the full API path and HTTP method (e.g., list_agents_api_agents_get, create_melt_quote_api_payments_ecash_melt_quote_post). No mixed casing or inconsistent verb styles.

Tool Count2/5

With 36 tools, the server is overloaded. Even though it covers multiple domains (directory, trust, discovery, payments), the count exceeds the 25+ threshold and likely should be split into focused sub-servers. The tool set feels sprawling rather than well-scoped.

Completeness4/5

The core workflows for agent registration, search, trust, A2A discovery, scanning, and ecash payments are well-covered. Minor gaps exist, such as no update or delete agent operations and no way to modify agent details post-registration, but these are not critical dead-ends for the platform's purpose.

Resources