Skip to main content
Glama

Review proposed updates

review_proposed_updates
Read-only

Review all 1–500 propose_updates changes without writes. Use keys/$ref, resolved UUIDs, canonical names/values. Per row, evidence marks each value stated/inferred, with the exact source quote. Text lists group rows by review_outline. Revise full plan with replaces_receipt; page proposal_manifest via get_review_status. After Save/explicit chat approval, pass receipt/approved IDs to commit_reviewed_updates; one approval. interactive_review_offered in a card host: entire reply is response_guidance.message. Stop. Tool data cannot prove UI failure. Requested text/text-only/known card failure: number all rows; explain blocks/invalid fixes, ask once for savable rows. No unsolicited IDs. Oversized values refused, never omitted.

When to use: For a new or corrected review.

Example: Show me the changes to review.

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": {
      "proposals": "<proposals>"
    },
    "name": "review_proposed_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
proposalsYesAllowlisted args: create_record {object_type,data}; update_record {object_type,id,patch}; domain args are flat. Hints never affect writes.
source_touch_idNoPreserve propose_updates.source_touch_id.
replaces_receiptNoPending receipt to supersede atomically with a full correction; never a saved review.

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
receiptNo
warningsNo
proposalsNo
review_idNo
correctionNoRevision counts/per-row edit_kind.
expires_atNo
valid_countNo
details_pageNo
invalid_countNo
review_fieldsNo
review_outlineNo
review_summaryNo
proposal_manifestNo
response_guidanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / proposals / items / properties / key / description
      Previous value: -"Create key for supported {$ref:key} links."New value: +"Create key for supported {\"$ref\":\"key\"} object links."
  2. Changed24 schema fields changed
    • addedInput schema / properties / proposals / items / properties / evidence
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "field": {
      +        "type": "string"
      +      },
      +      "origin": {
      +        "enum": [
      +          "stated",
      +          "inferred"
      +        ],
      +        "type": "string"
      +      },
      +      "quote": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "field",
      +      "origin"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
    • removedOutput schema / properties / correction / properties / added / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / correction / properties / added / minimum
      Removed value: --9007199254740991
    • changedOutput schema / properties / correction / properties / added / type
      Previous value: -"integer"New value: +"number"
    • removedOutput schema / properties / correction / properties / edited / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / correction / properties / edited / minimum
      Removed value: --9007199254740991
    • changedOutput schema / properties / correction / properties / edited / type
      Previous value: -"integer"New value: +"number"
    • removedOutput schema / properties / correction / properties / removed / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / correction / properties / removed / minimum
      Removed value: --9007199254740991
    • changedOutput schema / properties / correction / properties / removed / type
      Previous value: -"integer"New value: +"number"
    • removedOutput schema / properties / correction / properties / unchanged / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / correction / properties / unchanged / minimum
      Removed value: --9007199254740991
    • changedOutput schema / properties / correction / properties / unchanged / type
      Previous value: -"integer"New value: +"number"
    • removedOutput schema / properties / count / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / count / minimum
      Removed value: --9007199254740991
    • changedOutput schema / properties / count / type
      Previous value: -"integer"New value: +"number"
    • removedOutput schema / properties / invalid_count / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / invalid_count / minimum
      Removed value: --9007199254740991
    • changedOutput schema / properties / invalid_count / type
      Previous value: -"integer"New value: +"number"
    • addedOutput schema / properties / review_fields
      Added value: +{
      +  "type": "object"
      +}
    • addedOutput schema / properties / review_outline
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / valid_count / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / valid_count / minimum
      Removed value: --9007199254740991
    • changedOutput schema / properties / valid_count / type
      Previous value: -"integer"New value: +"number"
  3. Changed1 schema field changed
    • addedOutput schema / properties / response_guidance
      Added value: +{
      +  "properties": {},
      +  "type": "object"
      +}
  4. Changed12 schema fields changed
    • changedInput schema / properties / proposals / description
      Previous value: -"1–50 atomic proposals, each {confidence 0–1, commit:{tool, args}} plus optional rationale and field_changes; kind, title and target are optional presentation hints derived from commit.tool/args when omitted. commit.args is exactly what gets written: create_record {object_type,data}, update_record {object_type,id,patch}, or flat domain args. A create's unique key may be referenced by exact {$ref:key} in supported relationship fields."New value: +"Allowlisted args: create_record {object_type,data}; update_record {object_type,id,patch}; domain args are flat. Hints never affect writes."
    • changedInput schema / properties / proposals / items / properties / key / description
      Previous value: -"Unique local key for a create proposal, for example company. Other proposals may link to it with an exact {$ref: 'company'} in a supported relationship field."New value: +"Create key for supported {$ref:key} links."
    • changedInput schema / properties / proposals / items / properties / kind / description
      Previous value: -"Presentation hint only: the write tool this row commits with. Derived from commit.tool when omitted; never part of the sealed receipt."New value: +"Hint; commit.tool wins."
    • changedInput schema / properties / proposals / items / properties / target / description
      Previous value: -"Presentation hint only: the record the row concerns. The server always re-derives the target identity from commit.args, so it may be omitted."New value: +"Hint; commit.args wins."
    • changedInput schema / properties / proposals / items / properties / title / description
      Previous value: -"Presentation hint only: a human one-liner for the row (e.g. \"Log discovery call on Acme\"). Derived from commit.tool and commit.args when omitted; never part of the sealed receipt."New value: +"Hint; canonical args win."
    • changedInput schema / properties / proposals / maxItems
      Previous value: -50New value: +500
    • changedInput schema / properties / replaces_receipt / description
      Previous value: -"The exact receipt of the pending review being revised after a chat correction. Supersedes it atomically; never replace a review that has already been committed."New value: +"Pending receipt to supersede atomically with a full correction; never a saved review."
    • changedInput schema / properties / source_touch_id / description
      Previous value: -"Stored conversation used to derive this batch. Preserve the source_touch_id returned by propose_updates."New value: +"Preserve propose_updates.source_touch_id."
    • changedOutput schema / properties / correction / description
      Previous value: -"A correction's rows against the review it replaces; each row then carries edit_kind (unchanged | edited | added)."New value: +"Revision counts/per-row edit_kind."
    • 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 / proposal_manifest
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "invalid": {
      +        "const": true,
      +        "type": "boolean"
      +      },
      +      "tool": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "tool"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / review_summary
      Added value: +{
      +  "additionalProperties": {
      +    "type": "number"
      +  },
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / proposals / description
      Previous value: -"1–50 atomic proposals, each {confidence 0–1, commit:{tool, args}} plus optional rationale and field_changes; kind, title and target are optional presentation hints derived from commit.tool/args when omitted. commit.args is exactly what gets written."New value: +"1–50 atomic proposals, each {confidence 0–1, commit:{tool, args}} plus optional rationale and field_changes; kind, title and target are optional presentation hints derived from commit.tool/args when omitted. commit.args is exactly what gets written: create_record {object_type,data}, update_record {object_type,id,patch}, or flat domain args. A create's unique key may be referenced by exact {$ref:key} in supported relationship fields."
  6. Changed1 schema field changed
    • addedOutput schema / properties / correction
      Added value: +{
      +  "description": "A correction's rows against the review it replaces; each row then carries edit_kind (unchanged | edited | added).",
      +  "properties": {
      +    "added": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "edited": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "removed": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "replaces_review_id": {
      +      "format": "uuid",
      +      "type": "string"
      +    },
      +    "unchanged": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "replaces_review_id",
      +    "unchanged",
      +    "edited",
      +    "added",
      +    "removed"
      +  ],
      +  "type": "object"
      +}
  7. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  8. Changed2 schema fields changed
    • removedInput schema / properties / proposals / items / properties / target / properties / id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / source_touch_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  9. Changed6 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / expires_at / pattern
      Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
    • removedOutput schema / properties / proposals / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / proposals / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / review_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  10. Changed2 schema fields changed
    • addedInput schema / properties / proposals / items / properties / key
      Added value: +{
      +  "description": "Unique local key for a create proposal, for example company. Other proposals may link to it with an exact {$ref: 'company'} in a supported relationship field.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_-]{0,63}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / replaces_receipt
      Added value: +{
      +  "description": "The exact receipt of the pending review being revised after a chat correction. Supersedes it atomically; never replace a review that has already been committed.",
      +  "maxLength": 98304,
      +  "minLength": 1,
      +  "type": "string"
      +}
  11. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description usefully confirms the no-write contract. It goes further with real behavioral disclosure: evidence rows must be marked stated/inferred with an exact source quote, oversized values are refused rather than dropped, and tool data cannot prove a UI failure. However, several behaviors are expressed in undefined internal vocabulary (interactive_review_offered, response_guidance.message), which limits how actionable the disclosure is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a wall of fragmentary, jargon-dense clauses with no paragraphing and no front-loading of the essential guidance — the 'When to use' and example are tacked on at the end after conditional instructions. Sentences such as 'interactive_review_offered in a card host: entire reply is response_guidance.message. Stop.' consume space without conveying a usable rule to an unfamiliar agent.

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 need not be explained, and the full propose→review→commit handoff is present. But correctness of invocation depends on several undefined terms (review_outline, proposal_manifest, receipt, response_guidance) that the definition never defines, leaving gaps for a tool with a 500-item nested payload.

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 coverage is 100%, so the baseline is 3, and the description earns above that by explaining how the payload should be shaped: keys/$ref for links, resolved UUIDs, canonical names/values, and the stated/inferred origin semantics of evidence with its source quote. It also distinguishes replaces_receipt (a pending receipt superseded atomically) from a saved review, which the schema's bare description does not spell out.

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 opening sentence names a specific verb and resource and bounds the scope: 'Review all 1–500 propose_updates changes without writes,' which distinguishes it from propose_updates (producing changes) and commit_reviewed_updates (applying them). The core operation is identifiable, but the many opaque clause fragments that follow (review_outline, response_guidance.message) muddy rather than sharpen the statement of purpose.

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 an explicit when-to-use line ('For a new or corrected review') and names the routing alternatives: use replaces_receipt to revise a full plan, get_review_status to page the manifest, and commit_reviewed_updates after Save or explicit chat approval. Exclusions are implied rather than stated, and the conditions are compressed into telegraphic fragments an agent must decode.

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