Skip to main content
Glama

Ratings vs price

get_ratings
Read-onlyIdempotent

Customer ratings for every brand at an airport (overall and sub-scores: value for money, collection time, condition, cleanliness and more, with review counts) next to each brand's price index.

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": {
      "airport": "<airport>"
    },
    "name": "get_ratings"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook back for rating change. Default 30.
airportYesIATA airport code, e.g. AKL, SYD, LHR, MAD. See list_airports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description goes beyond them by disclosing what comes back: overall and sub-scores (value for money, collection time, condition, cleanliness), review counts, and a price index per brand. That return-content detail is valuable since no output schema exists. It says nothing about freshness, rate limits, or how ratings and price are aligned, keeping it at 4.

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?

A single front-loaded sentence with no filler; the parenthetical sub-score list earns its place because no output schema describes them. Slightly long and list-heavy, but nothing is wasted.

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?

For a low-risk read-only two-parameter tool with a fully documented schema and annotations covering safety, the description supplies the missing piece: what the response contains. Only the days window's effect on output is left solely to the schema, which is acceptable.

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 IATA code example and the 1-365 range on days. The description adds no meaning beyond that — notably it never mentions the days lookback for rating change, even though that is the one parameter an agent might misread.

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?

"Customer ratings for every brand at an airport ... next to each brand's price index" names a specific resource and scope (all brands at one airport) and the juxtaposition with price index, which separates it from single-brand siblings like get_brand_position. It never explicitly contrasts itself with those siblings, so it stops short of a 5.

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?

"for every brand at an airport" implies this is the batch/all-brands view rather than a single-brand lookup, which is usable guidance. There is no explicit when-to-use or when-not-to-use statement and no named alternative, so usage is only inferred.

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