Skip to main content
Glama

decide_review

Selected reviewer: record your signed Review of exactly this result and funded terms. Your verdict, rather than an operator-selected quality score, governs acceptance.

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": {
      "reviewId": "<reviewId>",
      "approved": "<approved>",
      "deadline": "<deadline>",
      "signature": "<signature>"
    },
    "name": "decide_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
approvedYes
deadlineYes
reviewIdYes
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully states that the reviewer's verdict governs acceptance, but it omits whether the decision is final or reversible, what permissions are required, how signatures are verified, and what happens if the deadline is missed.

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?

The description is two tight sentences and front-loads the actor and action. The contrast with an 'operator-selected quality score' adds useful context rather than wasted words.

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?

This is a consequential mutation-like tool with four required parameters, no annotations, and no output schema. The description states the core acceptance effect but lacks the parameter semantics and operational context needed for an agent to invoke it confidently.

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 four required parameters. The description hints at signature ('signed Review'), verdict ('approved'), and the reviewed result ('exactly this result'), but it never explains reviewId, deadline, or the expected format/meaning of the signature parameter.

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 uses a specific verb and resource: 'record your signed Review' with a verdict that 'governs acceptance.' It identifies the actor as the 'Selected reviewer' and the object as 'exactly this result and funded terms,' making the tool distinguishable from read/request review siblings, though the domain terms remain somewhat abstract.

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?

The phrase 'Selected reviewer' implies the usage condition: call this when you are the selected reviewer submitting a decision. However, it does not explicitly mention alternatives such as read_review, request_review, or review_inbox, nor does it state when not to use the tool.

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