Skip to main content
Glama

Continue a Review Shift

continue_review_shift
Read-onlyIdempotent

Next page of the book being reviewed. Call it straight after finishing a page until the check or the stretch the user chose is done, and again when they ask for more. Pass every field of next from the previous page (book, plan, and step or after), and volunteer_code. Returns the same shape as start_review_shift; follow how_to_run again. When page is null, read message: the book's check is complete or the book has ended; say so and offer what message offers.

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": {
      "book": "<book>",
      "volunteer_code": "<volunteer_code>"
    },
    "name": "continue_review_shift"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYesnext.book from the previous page
planNonext.plan from the previous page
stepNonext.step from the previous page (a paired check)
afterNonext.after from the previous page (reading in order)
volunteer_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / after / description
      Previous value: -"next.after from the previous page"New value: +"next.after from the previous page (reading in order)"
    • addedInput schema / properties / plan
      Added value: +{
      +  "description": "next.plan from the previous page",
      +  "enum": [
      +    "paired",
      +    "walk"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / step
      Added value: +{
      +  "description": "next.step from the previous page (a paired check)",
      +  "type": "number"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "book",
      -  "after",
      -  "volunteer_code"
      -]New value: +[
      +  "book",
      +  "volunteer_code"
      +]
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the termination contract: when page is null the check is complete or the book has ended, and the agent should read message, report it, and offer what message offers. That conditional end-state behavior is genuinely useful context an agent could not derive from annotations, though auth/volunteer_code requirements and any failure modes are left unstated.

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?

Four compact sentences, front-loaded with the core action and then the calling cadence, the state-passing rule, the return shape, and the null-page case. There is no filler, though the dense clause chain ('until the check or the stretch the user chose is done') takes a second read.

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 stateful pagination tool with no output schema, the description covers the loop, the state passing, and the terminal condition. Its main weakness is outsourcing the return shape to 'the same shape as start_review_shift' and referring to 'page' and 'message' as response fields without ever saying they are response fields, so the agent depends on prior knowledge of the sibling tool.

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?

With 80% schema coverage the baseline would be 3, but the description adds real meaning: all fields of next from the previous page must be passed back verbatim, and the 'step or after' phrasing signals that the two paging parameters are alternatives depending on the chosen plan. That coupling is not stated in the schema, where each field is documented only as 'next.X from the previous page'.

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 names a specific action and resource: fetching the next page of the book under review, with the paging state carried forward from the prior page. It is clearly distinguishable from start_review_shift (which begins the shift) and submit_page_review (which sends a review back), though the opening sentence is a fragment that only becomes fully clear from the following sentences.

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 explicit trigger conditions: call it immediately after finishing a page, keep calling until the chosen check or stretch is complete, and call again when the user asks for more. That is strong when-to-use guidance, but it never states the inverse boundary (e.g. that a new shift should go to start_review_shift rather than this tool), leaving that routing implicit.

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.