Café QR

Guest feedback

get_feedback

Read-onlyIdempotent

Guest ratings (1 to 5 stars) and comments, default the last 30 days: average, star counts, low ratings not yet followed up, and the latest comments. Set maxRating to 2 to see only complaints.

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": "get_feedback"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last day, YYYY-MM-DD, included. Overrides period.
`cafe`	No	Which café, by name or slug. Only needed when the person has more than one (see list_my_cafes).
`from`	No	First day, YYYY-MM-DD. Overrides period.
`limit`	No	How many comments, default 20.
`period`	No	A named period on the café's clock. Weeks start Monday.
`maxRating`	No	Only ratings at or below this.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does: the implicit 30-day lookback when no dates are given, plus the shape of the payload including a 'not yet followed up' flag that carries actionable meaning. No permissions, limits, or pagination caveats are mentioned.

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

Conciseness5/5

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

Two sentences, no filler. The content list comes first and the actionable tip (maxRating=2 for complaints) is placed where it will be read, so nothing is buried.

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?

There is no output schema, so the description must describe return values — and it does, listing the four components an agent will receive. With annotations covering safety and full schema coverage on inputs, no material gap remains for a 6-parameter read tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by giving semantic intent for maxRating ('to see only complaints') and by clarifying that the 30-day window is a default that period/from/to override, which is more than the schema's per-field text conveys.

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 the resource precisely (guest ratings 1-5 and comments) and enumerates the returned aggregates (average, star counts, unfollowed low ratings, latest comments), so the agent knows exactly what data arrives. It lacks an explicit verb and never distinguishes itself from siblings like get_sales_summary, but the resource is distinct enough that confusion is unlikely.

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

Usage Guidelines4/5

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

It states the default window (last 30 days) and gives a concrete call pattern: 'Set maxRating to 2 to see only complaints.' That is actionable usage guidance rather than a bare description. It stops short of explicit when-not-to-use or naming an alternative tool.

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

All Café QR 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?