Reel-E

Revision notes status

check_revision_notes

Read-onlyIdempotent

Where the latest revision notes stand: each note's fix, whether it was made, and how the re-check judged it (fixed, better, not fixed). A note counts as fixed only when this says so.

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": {
      "listingId": "<listingId>"
    },
    "name": "check_revision_notes"
  }
}

Input Schema

Name	Required	Description	Default
`listingId`	Yes	Listing id from list_listings.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real semantic context beyond that: the three verdict categories (fixed, better, not fixed) and the authority rule that only this tool's output can declare a note fixed — behavior an agent cannot infer from annotations or schema.

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 sentences, front-loaded with the resource and what is returned, with no filler. The opening clause 'Where the latest revision notes stand' is slightly informal but still earns its place as the scope statement.

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?

An output schema exists, so return values need not be spelled out, and the description nonetheless supplies the meaning of the verdict values. For a single-parameter read tool this is close to complete; the only gap is the absence of any relationship to review_revision_notes.

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% and the single listingId parameter is documented as coming from list_listings, so the schema carries the parameter burden. The description adds no format, constraint, or error semantics for the parameter, which is acceptable at this coverage level but not additive.

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 resource (the latest revision notes) and states exactly what is reported: each note's fix, whether it was made, and the re-check verdict. An agent can tell this is a status/read tool rather than a mutation, though it does not distinguish itself from the sibling review_revision_notes, which plausibly overlaps.

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 implied rather than stated: 'A note counts as fixed only when this says so' tells the agent to consult this tool to confirm fixes, but there is no explicit when-to-use/when-not-to-use guidance and no routing to the similarly named review_revision_notes sibling.

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

All Reel-E tools Inspect

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

Need Help?