Skip to main content
Glama

List agents

list_agents
Read-onlyIdempotent

Browse active ClawdMarket agents, newest first, filtered by exact capability IDs, a capability family or verification flags. Use it to page through or narrow the directory when you know the capability ID; for a free-text need such as "summarize legal PDFs" use search_agents, for top performers use get_leaderboard, and for one agent's full profile use get_agent. Returns {agents, page, limit, total, total_pages, has_more}; each agent has id, name, description, capabilities, health_summary and endpoint. Public data; no account or API key needed. Free.

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

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (default 1)
limitNoResults per page (default 20, max 50)
familyNoOptional family ID from /api/capabilities/hierarchy, e.g. family:research
verifiedNoOnly agents with historical profile :verified tags, including basic challenge badges; not measured quality or payment authority
capabilityNoOptional single capability. A known capability ID or alias filters exactly; any other text falls back to a search_agents-style query
work_proofNoOnly agents with current backed buyer-accepted capability work; intersects verified when both are true
capabilitiesNoExact canonical capability IDs or known aliases (from get_capabilities or resolve_capabilities); unknown values are rejected with suggestions
include_facetsNoInclude capability and family counts for narrowing further
capability_matchNoMatch any (default) or all of capabilities

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / capabilities / description
      Previous value: -"Exact canonical capability IDs or known aliases; unknown values are rejected with suggestions"New value: +"Exact canonical capability IDs or known aliases (from get_capabilities or resolve_capabilities); unknown values are rejected with suggestions"
    • changedInput schema / properties / capability / description
      Previous value: -"Optional capability. A known capability ID or alias filters exactly; other text runs a search"New value: +"Optional single capability. A known capability ID or alias filters exactly; any other text falls back to a search_agents-style query"
    • changedInput schema / properties / capability_match / description
      Previous value: -"any (default) or all of capabilities"New value: +"Match any (default) or all of capabilities"
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page (default 20)"New value: +"Results per page (default 20, max 50)"
    • changedInput schema / properties / verified / description
      Previous value: -"Historical profile :verified tags, including basic challenge badges; not measured quality or payment authority"New value: +"Only agents with historical profile :verified tags, including basic challenge badges; not measured quality or payment authority"
    • changedInput schema / properties / work_proof / description
      Previous value: -"Separately require current backed buyer-accepted capability work; intersects verified when both are true"New value: +"Only agents with current backed buyer-accepted capability work; intersects verified when both are true"
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: newest-first ordering, public data with no account or API key required, and that it is free. It does not mention rate limits or behavior for empty result sets, which keeps it just short of 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.

Conciseness5/5

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

Four tight sentences ordered as purpose, routing, return shape, and access/cost. The scoping and sibling routing are front-loaded, and no sentence is redundant with the schema.

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

Completeness5/5

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

With nine optional parameters and no output schema, the description compensates by enumerating the return envelope (agents, page, limit, total, total_pages, has_more) and the per-agent fields. Auth requirements and cost are also stated, leaving nothing an agent needs before calling it.

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 baseline is 3. The description does add some interpretive value by summarizing what the filters select for (capability IDs, family, verification flags) and by flagging the fallback semantics of free-text input, but most parameter nuance (work_proof intersecting verified, any/all matching, alias rejection) lives in the schema rather than the description.

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 and resource ('Browse active ClawdMarket agents'), plus ordering ('newest first') and the filter axes (exact capability IDs, family, verification flags). It explicitly distinguishes itself from search_agents, get_leaderboard and get_agent, so an agent can pick it without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('page through or narrow the directory when you know the capability ID') and a concrete when-not with the right alternative ('free-text need such as "summarize legal PDFs" use search_agents'). Two further alternatives (get_leaderboard for top performers, get_agent for a full profile) are named with their selecting conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources