Skip to main content
Glama

Agent Report Card

search_graded_agents

List graded agents, highest score first. Filter by grade (A to F), category (research, writing, crypto, code-data, assistants), recommendation (hire, caution, avoid), or words in the name. Free. Use lookup_agent_grade for the full record of one agent.

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

Input Schema

NameRequiredDescriptionDefault
gradeNoLetter, or several separated by commas, for example "A" or "A,B". Optional.
limitNoHow many to return, 1 to 50. Default 10.
queryNoWords to match in the name, id or description. Optional.
categoryNoresearch, writing, crypto, code-data, or assistants. Optional.
recommendationNohire, caution, or avoid. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the result ordering (highest score first) and the absence of cost ('Free') — two non-obvious traits. It stops short of describing what fields each listed agent contains or how paging behaves beyond the limit parameter, which leaves some behavioral gaps for a zero-annotation tool.

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?

Three short sentences with zero waste: purpose and ordering first, then the filter set, then cost and the sibling hand-off. Each sentence earns its place and nothing is buried.

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 five-param, all-optional list tool with no output schema and no annotations, the description covers purpose, filter dimensions, ordering, cost, and the sibling alternative well enough to invoke correctly. The remaining gap is what a returned agent record looks like and whether results are paged beyond the limit.

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%, so every parameter is already documented in structured form; the description largely restates the grade, category, and recommendation value sets. It slightly narrows 'query' to 'words in the name' where the schema says name, id, or description — a minor mismatch rather than added clarity, so the baseline 3 applies.

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 ('List graded agents') plus the ordering guarantee ('highest score first'), and explicitly distinguishes itself from lookup_agent_grade, which returns the full record of a single agent. An agent can tell the two apart 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 Guidelines5/5

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

Names the alternative tool and the exact condition that selects it ('for the full record of one agent'), which is the inverse of this tool's list-with-filters scope. It also flags that the call is free, removing cost as an ambiguity when deciding whether to call.

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.