Crawlora MCP

tripcom_hotel_detail

Read-only

Fetch one Trip.com hotel's normalized detail data, including location, rating breakdown, policies, and facilities. Use tripcom_hotels_search to discover a hotel and obtain its identifier.

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>",
      "slug": "<slug>"
    },
    "name": "tripcom_hotel_detail"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Trip.com hotel id, from a prior Search call's hotel_id field or the numeric segment of a /hotels/{slug}-hotel-detail-{id}/ URL.
`slug`	Yes	Optional slug segment for a nicer canonical URL (e.g. the district/city slug from a Search result's url). Not required and not validated by Trip.com.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that data is 'normalized,' which is mildly useful, but says nothing about failure modes (e.g. invalid/missing id), freshness, or whether the slug affects the response — extra value is modest against an already-covered annotation set.

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, zero filler, with the core action and the returned data categories front-loaded before the prerequisite call. Every clause 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?

An output schema exists, so return values need not be re-explained, and the description correctly focuses on purpose and the search prerequisite. Combined with read-only annotations and complete parameter docs, this is nearly self-sufficient; only minor behavioral detail is absent.

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%, so both the id and slug parameters (including their provenance and the optional-but-unvalidated nature of slug) are fully documented in the schema. The description adds no parameter-level detail beyond what structured data provides, so 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?

States a specific verb (Fetch) and resource (one Trip.com hotel's normalized detail data), then enumerates the content categories (location, rating breakdown, policies, facilities). It also names the sibling tool tripcom_hotels_search, letting an agent distinguish it from the search endpoint 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?

Explicitly instructs the agent to use tripcom_hotels_search first to discover a hotel and obtain its identifier, establishing the correct call ordering and data dependency. It stops short of stating any when-not conditions or alternative detail endpoints, but the primary workflow is clear.

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

All Crawlora MCP 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?