Skip to main content
Glama

get_review_feedback

Retrieve reviewer verdicts and comments on recorded decisions, and turn rejected decisions and comments into instructions for the agent to follow.

Instructions

Get reviewer verdicts and comments on your earlier decisions. Rejected decisions and comments are instructions to follow.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real semantics beyond a bare read: verdicts and comments are returned and 'Rejected decisions and comments are instructions to follow,' which tells the agent to act on rejections. It says nothing about read-only nature, freshness, whether feedback is consumed/deduplicated on read, or volume.

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?

Two short sentences, zero padding, with the subject (what you get) front-loaded and the actionable constraint second. Every sentence carries weight.

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 zero-parameter read tool with an output schema, the description covers what comes back and how to treat rejections. The one meaningful omission is lifecycle behavior: whether the same feedback is returned on repeated calls, which matters for an agent polling after each decision.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the schema is complete as-is. Baseline 4 applies.

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 gives a specific verb and resource: 'Get reviewer verdicts and comments,' plus scope 'on your earlier decisions,' which ties it to the record_decision sibling. It never names or contrasts an alternative tool, so differentiation is implied rather than stated.

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 phrase 'on your earlier decisions' implies this is called after recording a decision, and the second sentence tells the agent how to act on the result. There is no explicit when-to-use, when-not-to-use, or named alternative among record_decision and show_behavior.

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

Deploy Server

Other Tools