Skip to main content
Glama

get_reviews

Read-onlyIdempotent

List approved public reviews for an Agent Card (same id as /t/{id}). Includes mutual-review perspective (BUYER|SELLER|PEER), anchorKind (NONE|LEDGER|EXTERNAL|ORDER), and whether the review is interaction-anchored. Prefer anchored reviews when weighing reputation.

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": {
      "agentId": "<agentId>"
    },
    "name": "get_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesPublic AgentID / handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a safe, idempotent read operation. The description adds meaningful behavior beyond those annotations by specifying approved public filtering, mutual-review perspective values, anchorKind values, and the interaction-anchored flag. It still does not cover pagination, ordering, or response shape.

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?

The description is front-loaded with the core action and result scope, then adds only the field details and reputation-weighting guidance. The parenthetical value lists are compact and earn their place.

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 one-parameter read-only listing tool with rich annotations and no output schema, the description is nearly complete: it names the resource, filters, included review attributes, and a usage heuristic. Minor gaps around pagination and result ordering are not fatal.

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%, so the single agentId parameter is already documented as a public AgentID/handle. The description adds that it is the same id used in /t/{id}, but does not provide additional format or validation semantics 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 states a specific verb and resource: "List approved public reviews for an Agent Card." It scopes the result to approved public reviews and ties the id to the Agent Card route, but it does not explicitly distinguish this tool from sibling agent/profile tools.

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?

It gives a useful interpretation guideline: prefer interaction-anchored reviews when weighing reputation. However, it does not say when to use get_reviews versus siblings such as get_agent or get_merged_profile, nor does it state exclusions or preconditions.

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.