Skip to main content
Glama

Pagetool

Record a review of one exact site version

record_review

Reviewer token only. Records pass or revise for one exact version of a site (from list_reviews). The operator token can publish only a version whose latest review is a pass; any edit makes a new version.

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": {
      "site_key": "<site_key>",
      "version": "<version>",
      "verdict": "<verdict>"
    },
    "name": "record_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional summary of the review (up to 2000 characters).
itemsNoWhat must change (up to 50 short items). Required in practice for revise.
verdictYespass lets the operator publish this exact version; revise blocks it until a new version passes.
versionYesThe exact version you reviewed: current_draft_version (before publish_site) or current_staged_version (before publish_staged) from list_reviews. Any later edit makes a new version that needs its own review.
site_keyYesThe site you reviewed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=false but say nothing about authorization or consequences; the description fills both gaps by naming the required token type and spelling out that a revise verdict blocks publishing while a pass unblocks it. It does not disclose what the call returns or what happens if a review for that version already exists, which is a remaining gap for a non-idempotent write.

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 sentences, no waste, with the hardest constraint ("Reviewer token only.") front-loaded before the workflow detail. The final sentence about edits creating new versions is the one piece of context an agent would otherwise get wrong.

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 five-parameter mutation with no output schema and no annotations covering authorization, the description supplies the auth model and the publish-blocking effect, which is what an agent most needs. It is slightly thin on the return value and on re-review/overwrite behavior, but the core calling decision is well supported.

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%, so all five parameters, including the verdict enum semantics and version provenance, are already documented in the schema. The description restates the pass/revise consequence that the schema's verdict field also states, adding essentially no new meaning beyond structured data. Baseline 3 applies.

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 gives a specific verb and resource ("Records pass or revise for one exact version of a site") and pins the scope to a single version, pointing at list_reviews as the source of that version. It is clearly distinct from list_reviews, but it doesn't contrast itself with adjacent actions in the workflow (publish_site, publish_staged, restore_version), so sibling differentiation is only partial.

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 states an explicit caller constraint ("Reviewer token only") and explains the downstream condition ("The operator token can publish only a version whose latest review is a pass"), which tells the agent when this call is meaningful. It stops short of saying when NOT to call it -- e.g. that recording against a superseded version is pointless -- though the note that "any edit makes a new version" implies it.

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