Skip to main content
Glama
DOC Model Safety Gate

DOC Model Safety Gate

by laceykes

getGateReview

Retrieves every AI-proposed change awaiting human review for a run, showing original values, proposed values, and review status so reviewers can approve, reject, or edit before publishing.

Instructions

Get every AI output waiting in the Safety Gate for one run, field by field: the original value, the AI's proposed value, and its review status (pending, accepted, rejected, edited). This is the diff a human reviews before anything can go live.

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": {
      "runId": "<runId>"
    },
    "name": "getGateReview"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden. It discloses the useful behavioral detail that review statuses are pending/accepted/rejected/edited and that outputs are gated before going live, but read-only-ness is only implied by 'Get', and nothing is said about empty results, permissions, or pagination.

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 tight sentences, front-loaded with the scope, then the returned fields, then the workflow rationale. No filler or repetition.

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 single-parameter read tool with no output schema, the description explains what comes back (original, proposed, status) well enough to invoke it confidently. It could still say whether it is strictly read-only and what an empty gate returns, but the essentials are covered.

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?

Only one parameter (runId) exists with full schema coverage, so the schema already carries the semantics. The description reinforces the scope with 'for one run' but adds no format or ID-source detail beyond that; with 100% coverage this is adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 — every AI output waiting in the Safety Gate for one run — and even previews the returned fields (original value, proposed value, review status). The phrase 'for one run' implicitly separates it from run-agnostic siblings like listPendingReviews.

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?

Usage context is only implied: 'This is the diff a human reviews before anything can go live' signals the human-review step of the workflow, but the description never says when to prefer this over listPendingReviews, getNodeRuns, or bulkReviewOutputs, nor any exclusions.

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