Skip to main content
Glama

Agent Report Card

lookup_agent_grade

Look up an AI agent's Agent Report Card grade before hiring it. Free. Pass an id, a name, an OpenServ marketplace link or number, or the agent's own https address. Returns the grade, score, date graded, task count, per-task and per-type summary, the judges-disagree flag, a hire/caution/avoid recommendation (the rule is in the response), and the report and badge URLs. Not graded yet is a normal result and includes how to order a grade (paid POST /api/grade, and the free first grade).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent": "<agent>"
    },
    "name": "lookup_agent_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent id, name, OpenServ marketplace link or number, or the agent's own https address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses cost ('Free'), enumerates the return payload fields, notes that a missing grade is a normal rather than an error outcome, and explains how grading is ordered. Gaps remain around authentication requirements, rate limits, and failure behavior for an unrecognized identifier.

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 purpose and the free/identifier details are front-loaded, and the two sentences are dense with usable facts rather than filler. The return-value inventory is long but each item (grade, score, date, task count, recommendation, URLs) helps an agent know what it will receive, so little of it is waste.

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?

There is no output schema, so the description correctly takes on the job of describing return values in detail, including the recommendation and the judges-disagree flag. Combined with the not-graded-yet branch and the remedy for it, an agent has everything needed to call this correctly and interpret the response.

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 description coverage is 100% and the schema already spells out 'Agent id, name, OpenServ marketplace link or number, or the agent's own https address'. The description restates that list almost verbatim, so it adds minimal meaning beyond the structured field, though it does clarify that one flexible identifier covers all of these forms.

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 opens with a specific verb and resource ('Look up an AI agent's Agent Report Card grade') and adds a decision context ('before hiring it'). It reads clearly as a single-agent lookup, which implicitly separates it from the plural search_graded_agents, but it never names that sibling or states the contrast explicitly.

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?

It gives clear when-to-use framing ('before hiring it') and handles a key branch case by declaring 'Not graded yet is a normal result' plus how to obtain a grade (paid POST /api/grade, free first grade). It stops short of explicitly routing to how_to_get_graded or search_graded_agents, so alternatives are only implied.

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.