Skip to main content
Glama
DOC Model Safety Gate

DOC Model Safety Gate

by laceykes

bulkReviewOutputs

Accept or reject every pending AI output in a run at once and return the reviewed count. Edited outputs require individual review.

Instructions

Accept or reject every pending AI output in a run at once. Returns how many outputs were reviewed. Bulk review does not support edited; review edited outputs one at a time with reviewOutput.

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>",
      "action": "<action>"
    },
    "name": "bulkReviewOutputs"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID
actionYesReview decision for all pending outputs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description still discloses the broad mutation scope, the fact that only pending outputs are reviewed, the unsupported edited-output case, and that the result is a count of reviewed outputs. It does not clarify atomicity, empty-run behavior, or whether edited outputs in a mixed run cause failure or are skipped.

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?

Three short sentences efficiently cover purpose and scope, return behavior, and the key limitation with its alternative. The most important selection information is front-loaded, and there is no unnecessary wording.

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 simple two-parameter operation, the definition provides the invocation context, supported decisions, affected outputs, result meaning, and sibling fallback. The remaining ambiguity about mixed edited/pending runs and bulk failure behavior keeps it from being fully complete, especially without annotations.

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

Parameters3/5

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

Schema description coverage is 100%, and both required parameters are already clear, including the accepted/rejected enum. The description reinforces the run-wide scope but adds no meaningful parameter syntax, format, or selection details beyond the schema.

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 uses specific verbs and scope: "Accept or reject every pending AI output in a run at once." It also distinguishes the bulk operation from reviewOutput, which handles edited outputs individually.

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

Usage Guidelines5/5

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

It gives a clear use case—applying one accept/reject decision to all pending outputs in a run—and an explicit exclusion. The instruction to "review edited outputs one at a time with reviewOutput" supplies both the when-not condition and the appropriate alternative.

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