Skip to main content
Glama

Get review status

get_review_status
Read-only

Read status/details; no approval or writes. Submitted returns frozen selection/outcomes; pending needs a decision; superseded needs the latest review; expired proves no first commit within retention. If unavailable/uncertain, inspect CRM before saving. Page exact details/outcomes via next_offset until null. Poll executing reviews with backoff.

When to use: Synchronize a review after chat approval or correction, using its unchanged receipt. Reads status only.

Example: Have those reviewed changes been saved?

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": {
      "receipt": "<receipt>"
    },
    "name": "get_review_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYesUnchanged review receipt.
details_limitNoDetail row limit, default 25; byte bounds may reduce it.
details_offsetNoExact-detail offset; follow details_page.next_offset.
outcomes_limitNoOutcome row limit, default 100; byte bounds may reduce it.
outcomes_offsetNoOutcome offset; follow outcomes_page.next_offset.

Output Schema

NameRequiredDescriptionDefault
noteNo
summaryNo
outcomesNo
confirmedNo
proposalsNo
review_idNo
details_pageNo
outcomes_pageNo
review_statusNo
request_statusNo
response_guidanceNo
superseded_by_review_idNo
frozen_selected_proposal_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / response_guidance
      Added value: +{
      +  "properties": {},
      +  "type": "object"
      +}
  2. Changed8 schema fields changed
    • addedInput schema / properties / details_limit
      Added value: +{
      +  "description": "Detail row limit, default 25; byte bounds may reduce it.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / details_offset
      Added value: +{
      +  "description": "Exact-detail offset; follow details_page.next_offset.",
      +  "maximum": 500,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / outcomes_limit
      Added value: +{
      +  "description": "Outcome row limit, default 100; byte bounds may reduce it.",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / outcomes_offset
      Added value: +{
      +  "description": "Outcome offset; follow outcomes_page.next_offset.",
      +  "maximum": 500,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / receipt / description
      Previous value: -"Unchanged receipt returned by review_proposed_updates for the review to inspect."New value: +"Unchanged review receipt."
    • addedOutput schema / properties / details_page
      Added value: +{
      +  "properties": {
      +    "next_offset": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "offset": {
      +      "type": "number"
      +    },
      +    "total": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "offset",
      +    "next_offset",
      +    "total"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / outcomes_page
      Added value: +{
      +  "properties": {
      +    "next_offset": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "offset": {
      +      "type": "number"
      +    },
      +    "total": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "offset",
      +    "next_offset",
      +    "total"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / proposals
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  4. Changed4 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / outcomes / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / summary / additionalProperties
      Removed value: -{}
  5. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, the description explains meaningful review states: submitted returns frozen outcomes, pending needs a decision, superseded needs the latest review, and expired indicates no first commit within retention. It also discloses pagination via next_offset until null and polling behavior with backoff.

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 definition is compact and front-loads the read-only constraint and state meanings. The telegraphic style is dense but efficient; the when-to-use and example sections are appropriately placed.

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?

Given the annotations, full schema coverage, and an output schema, the description covers the remaining agent-relevant context: state meanings, pagination, polling, and when to use the tool. Nothing important for correct invocation appears missing.

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?

Schema description coverage is already 100%, so the schema carries most parameter meaning. The description still adds useful semantics by emphasizing the unchanged receipt and explaining that exact details/outcomes should be paged via next_offset until null.

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: 'Read status/details' for a review, and explicitly contrasts with writes or approvals. It distinguishes the read-only nature from commit-style siblings, but does not name a specific alternative tool, keeping it just short of a 5.

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 a clear usage context: synchronize a review after chat approval or correction using its unchanged receipt. It also advises inspecting CRM when unavailable or uncertain and explains polling with backoff, but it does not explicitly name when-not or a sibling alternative.

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.

Resources