Skip to main content
Glama
Mipiti MCP Server
by Mipiti

Get Review Run

get_review_run

Fetch a read-only review run digest to inspect decisions and evidence, parked items, spend, notes, and any decision undos still available.

Instructions

A review run's digest: what it decided and on what evidence, what it parked, what it spent, its notes, and the undo of each decision (offered while that decision is still the latest of its subject). Read-only.

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": {
      "server_version": "<server_version>",
      "model_id": "<model_id>"
    },
    "name": "get_review_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNoThe run. Empty (default): your open run, else the model's runs, newest first.
model_idYesID of the threat model.
server_versionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.106.1

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the two most important traits: it is explicitly read-only, and the undo offer is conditional ('while that decision is still the latest of its subject'), which signals volatile, state-dependent output. It says nothing about permissions, result size, or what happens when no run exists, which is a real gap given zero annotation coverage.

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?

One tightly packed sentence that front-loads the payload and ends with the safety-relevant 'Read-only.' Nothing is wasted, though the comma-chained list of 'what it...' clauses takes a second read.

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

Completeness3/5

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

An output schema exists, so return values needn't be spelled out, and the description correctly emphasizes decision/undo state. However, for a tool with a required, undocumented parameter and several near-neighbor read tools, the definition omits the invocation-critical details an agent needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description adds no meaning to any parameter. Crucially, the required 'server_version' parameter is undocumented in both the schema and the description, so the tool cannot be invoked confidently from the definition alone; run_id's default semantics are also only in 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?

It names a specific resource (a review run) and enumerates the payload concretely: decisions, evidence, parked items, spend, notes, and undo state. An agent can tell this apart from the queue/playbook/close siblings by the content described, though the noun-phrase framing ('digest') is more evocative than a plain verb+resource statement.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus get_review_queue, get_review_playbook, or close_review_run, and no preconditions or exclusions. The only routing hint (empty run_id means your open run, else the model's newest runs) lives in the schema, not the description.

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