Skip to main content
Glama
Sign In

More Good Reviews

by com.moregoodreviews
OverviewDiscussionsAdmin

Get Review Page

getReviewPage
Read-onlyIdempotent

Get Review Page

Read one review page, including its fields, links, redirects, locations, and QR codes.

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": {
      "id": "<id>"
    },
    "name": "getReviewPage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id of the review page. This is the same id used in the public form query parameter.

Output Schema

NameRequiredDescriptionDefault
codeNoApplication-level status code mirroring HTTP 200 on success.
dataNoReview page configuration, including the records used to render it.
successNoIndicates whether the request completed successfully.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety and idempotency are covered. The description adds real value by enumerating the returned sub-resources (links, redirects, locations, QR codes), telling the agent this is a rich composite read rather than a flat record. It does not address error behavior for a missing id, but that gap is minor given the annotation coverage.

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?

Two short, front-loaded sentences with no filler; the only waste is that the first line restates the tool title verbatim. The content-bearing sentence about returned components comes immediately after.

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

Completeness5/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 spelled out, and annotations fully cover the read-only, idempotent safety profile. For a one-parameter lookup, the description supplies everything needed to select and call it correctly.

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% and the single `id` parameter is already documented in the schema as the numeric id also used in the public form query parameter. The description adds no additional meaning about the id, so the baseline of 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 uses a specific verb and resource ("Read one review page") and lists the components it returns (fields, links, redirects, locations, QR codes). The singular "one" implicitly contrasts with the plural sibling listReviewPages, but no sibling is named explicitly.

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: requiring an id and reading a single page suggests retrieval after looking up an id, but there is no explicit when-to-use versus listReviewPages or guidance on how to obtain the id. No exclusions or alternatives are stated.

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

All More Good Reviews toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources