Skip to main content
Glama

Place reviews

bl_reviews
Read-onlyIdempotent

Retrieve one page of a Balad place's newest user reviews with star ratings and rating breakdown; use pagination to collect additional review pages when needed.

Instructions

Get one page of user reviews of a place on Balad, newest first, with stars and the rating breakdown.

When more is true, call again with page+1. bl_place already includes the first few reviews.

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

Input Schema

NameRequiredDescriptionDefault
idYesPlace id from bl_search or bl_nearby.
pageNoPage (10 reviews each, 1-100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / id / description
      Previous value: -"Place id from bl_search or bl_nearby, e.g. 4Dvh6E79N49I2j."New value: +"Place id from bl_search or bl_nearby."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 10 reviews per page, newest first (1-100)."New value: +"Page (10 reviews each, 1-100)."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description adds the non-obvious parts: newest-first ordering and the presence of a `more` flag that drives the pagination loop. Since there is no output schema, disclosing the `more` field is genuinely useful behavior information, though it does not say what an empty or last-page response looks like.

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, front-loaded with the primary purpose, then the follow-up action. Every clause carries information an agent needs to call the tool and continue paginating; 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 two-parameter read tool with no output schema, the description covers the essentials: what is returned, ordering, page size (via schema), and how to continue. It leaves minor gaps about terminal/empty responses and total review counts, which an agent might want but can discover at runtime.

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 `id` provenance (from bl_search or bl_nearby) and page bounds of 1-100 with 10 reviews each are already documented in the schema. The description adds only the behavioral link between `page` and the `more` flag ('call again with page+1'), which is a modest increment over the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get a page of user reviews of a place), plus the ordering ('newest first') and payload contents ('stars and the rating breakdown'). It also distinguishes itself from the sibling bl_place, which 'already includes the first few reviews', so an agent can tell the two apart without opening either schema.

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?

Gives a clear invocation rule for pagination: 'When `more` is true, call again with page+1.' The note that bl_place already surfaces the first few reviews implicitly tells the agent when this tool is unnecessary, but that exclusion is only implied rather than stated as an explicit when-not rule.

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