Skip to main content
Glama

Preview Review Requests Tool

preview-review-requests
Read-only

Previews explicit completed jobs for review requests, including eligibility and skip reasons, without sending anything. Use to preview review requests in the connected business. Returns requested, eligible, skipped, destination_configured, default_channel, items, sent, scope.

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": {
      "job_ids": "<job_ids>"
    },
    "name": "preview-review-requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoOptional review-request channel preference.
job_idsYesExplicit job IDs to evaluate.

Output Schema

NameRequiredDescriptionDefault
sentYesSent flag; previews do not perform this action.
itemsYesBounded items records returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
skippedYesSkipped for the returned result.
eligibleYesEligible for the returned result.
requestedYesRequested for the returned result.
default_channelYesDefault channel used or returned by this tool.
destination_configuredYesWhether the review destination is configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "job_ids"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "default_channel": {
      +      "description": "Default channel used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "destination_configured": {
      +      "description": "Whether the review destination is configured.",
      +      "type": "boolean"
      +    },
      +    "eligible": {
      +      "description": "Eligible for the returned result.",
      +      "type": "integer"
      +    },
      +    "items": {
      +      "description": "Bounded items records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "requested": {
      +      "description": "Requested for the returned result.",
      +      "type": "integer"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "sent": {
      +      "description": "Sent flag; previews do not perform this action.",
      +      "enum": [
      +        false
      +      ],
      +      "type": "boolean"
      +    },
      +    "skipped": {
      +      "description": "Skipped for the returned result.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "requested",
      +    "eligible",
      +    "skipped",
      +    "destination_configured",
      +    "default_channel",
      +    "items",
      +    "sent",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so the safety profile is covered; 'without sending anything' reinforces it. The description does add that eligibility and skip reasons are surfaced, which is real behavioral context, but it says nothing about limits on which jobs qualify or how defaults are chosen.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, which is good. However, the trailing enumeration 'requested, eligible, skipped, destination_configured, default_channel, items, sent, scope' duplicates the output schema and burns roughly half the text on information an agent already has.

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?

With a full input schema, an output schema and clear read-only annotations, the definition covers enough for correct invocation. The main remaining gap is guidance about which jobs would be ineligible, which is arguably discoverable from the preview result itself.

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 coverage is 100%, so both parameters are already documented including the channel enum. The description's phrase 'explicit completed jobs' adds a constraint not obvious from the schema (jobs must be completed), but it never mentions the channel parameter or how it interacts with the default.

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?

Names a specific verb and resource (previews completed jobs for review requests) and adds the key qualifier 'without sending anything', which separates it from an actual send operation. It is clearer than the title alone, though it does not explicitly contrast itself with the many sibling preview-* tools.

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

Usage Guidelines2/5

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

'Use to preview review requests in the connected business' essentially restates the purpose sentence and adds only the connected-business scope. There is no guidance on when to prefer this over other preview tools, no prerequisites, and no exclusions.

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