Skip to main content
Glama

Place details

bl_place
Read-onlyIdempotent

Retrieve full details for a Balad place by ID, including address, phone numbers, opening hours, open-now status, rating, amenities, photos, and reviews.

Instructions

Get one place's full details from Balad: address, phones, hours, open now, rating, amenities, photos, reviews.

hours maps each weekday (شنبه..جمعه) to its hours; menu is the menu link. More reviews: bl_reviews; directions: bl_route with its lat/lng.

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_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlace id from bl_search or bl_nearby.
photosNoPhoto URLs to include (0-20).
reviewsNoRecent reviews to include (0-10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / photos / description
      Previous value: -"How many photo URLs to include (0-20)."New value: +"Photo URLs to include (0-20)."
    • changedInput schema / properties / reviews / description
      Previous value: -"How many recent reviews to include (0-10)."New value: +"Recent reviews to include (0-10)."
  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 declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile needs no restating. The description adds value beyond them by explaining output shape details that no output schema captures: `hours` maps each weekday (شنبه..جمعه) to its hours and `menu` is the menu link. It says nothing about failure modes for an invalid/expired id or rate limits, keeping it out of 5 territory.

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 short paragraphs, front-loaded with the core purpose, then a compact field-semantics note plus sibling routing. Every sentence carries distinct information and code formatting makes the field names scannable.

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?

With no output schema, the description usefully enumerates return fields and clarifies two of them (`hours`, `menu`), and annotations cover the safety profile. Minor omissions remain — no note on what happens with an unknown id or on how the photos/reviews counts affect payload size — but nothing essential for a successful call is missing.

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 schema already explains that `id` comes from bl_search/bl_nearby and that `photos` (0-20) and `reviews` (0-10) control inclusion counts. The description adds no further meaning about the parameters, so the baseline 3 applies.

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?

The description leads with a specific verb and resource ('Get one place's full details from Balad') and enumerates the exact returned fields (address, phones, hours, open now, rating, amenities, photos, reviews). Combined with 'one place', it clearly separates this single-record fetch from the list-style siblings like bl_search and bl_nearby.

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 routes the agent onward for adjacent needs: 'More reviews: bl_reviews' and 'directions: bl_route with its lat/lng', which names alternatives and the condition that selects them. It does not state a when-not-to-use case (e.g. when to prefer bl_search instead of resolving a known id), so it falls short of a full 5.

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