Skip to main content
Glama

review_next

Lease the next eligible review item for a session, optionally filtered by tags, kinds, scope, or namespace, to support mentor review workflows.

Instructions

Lease the next eligible review item for this session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "review_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNo
actor_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and 'Lease' is the only behavioral signal it gives. It never says what a lease guarantees, whether it is exclusive to the session, how long it lasts, whether it expires or must be released via submit_review, or what happens when no item is eligible.

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?

One front-loaded sentence with no filler or redundancy. The brevity is efficient rather than padded, though it shades into under-specification for a lease-style operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but for a tool whose core mechanic is leasing and filtering, the description leaves both unexplained. An agent cannot predict lock behavior, empty-result handling, or how to target a specific subset of review items.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, and the description mentions neither filters nor actor_handle. It says 'eligible' without revealing that eligibility is controlled by tags, kinds, namespace, and scope filters, leaving the main lever of the tool undocumented in both places.

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 ('Lease') and resource ('next eligible review item') plus a session scope, which is enough to separate it from submit_review or get_entry. It stops short of differentiating itself against any named sibling or explaining what 'eligible' means.

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 is only implied: an agent can infer this is the call you make to pull work into a review loop. There is no explicit when-to-use statement, no when-not-to-use, and no pointer to submit_review as the natural follow-up or to how filters change what is eligible.

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