Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

accor_search_details

Resolve an anonymous Accor search suggestion identifier to public place details: description, coordinates, viewport, radius, and address components.

Instructions

Accor place coordinates and viewport. Resolves an anonymous Accor search suggestion identifier to its description, coordinates, viewport, radius, and address components. It uses the same public place-details source as the Accor search box; booking, rates, rooms, reviews, and account data are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentifier returned by Accor search suggestions
sourceYesSuggestion source
languageNoOptional locale

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / source / enum
      Added value: +[
+  "google_places",
+  "hod_hotels"
+]
  2. Addedv1.16.2

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that it's a read-only lookup (resolves an identifier) and explicitly states exclusions (booking, rates, etc.). It doesn't mention error handling or rate limits, but for a simple lookup that's acceptable. It doesn't contradict any annotations.

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?

The description is two sentences, front-loaded with the tool's purpose ('Accor place coordinates and viewport'), followed by a concise explanation of what it does. No filler or redundancy—every sentence earns its place.

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 simple 3-param tool with no output schema, the description adequately lists the returned components (coordinates, viewport, radius, address). It also notes the data source (same as Accor search box) and exclusions, giving enough context for an agent to call it correctly. Minor gap: doesn't specify coordinate format, but that's not critical.

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% (each param has a description). The description adds minimal extra meaning—it clarifies that 'id' is an anonymous search suggestion identifier, which is already in the schema. It doesn't provide additional semantics beyond what the schema already documents, so baseline 3 is appropriate.

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?

Description clearly states the verb (resolves), the resource (Accor search suggestion identifier), and the output (description, coordinates, viewport, radius, address components). It also distinguishes itself from siblings by explicitly excluding booking, rates, rooms, reviews, and account data, making it clear it's for location details only.

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?

The description implies when to use it: when you have an anonymous search suggestion identifier and need coordinates/viewport. It doesn't explicitly name alternatives like accor_property, but it clarifies what it doesn't return, which guides selection. It could be more explicit about comparing to accor_property for full property details.

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

Deploy Server

Other Tools