Google Hotel Prices
Server Details
Search hotel prices, get best overall and best direct price in structured response. Get your developer token at https://Infoseek.ai/mcp
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
1 toolget_hotel_pricesARead-onlyInspect
Get hotel prices for an exact hotel stay using the hotel name, city, dates, and optional guest/address fields. This tool resolves the final Google Hotels link internally, then returns normalized best overall and best direct-booking prices for that stay in one call.
| Name | Required | Description | Default |
|---|---|---|---|
| hotel_city | Yes | Required hotel city. | |
| hotel_name | Yes | Required hotel name. | |
| hotel_state | No | Optional hotel state or province. | |
| hotel_street | No | Optional hotel street address. | |
| hotel_country | No | Optional hotel country. | |
| hotel_guest_count | No | Optional hotel guest count. Defaults to 2. | |
| hotel_check_in_date_yyyy_mm_dd | Yes | Required hotel check-in date in YYYY-MM-DD. | |
| hotel_check_out_date_yyyy_mm_dd | Yes | Required hotel check-out date in YYYY-MM-DD. |
Output Schema
| Name | Required | Description |
|---|---|---|
| meta | Yes | |
| results | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description adds valuable behavioral context: it discloses the internal mechanism ('resolves the final Google Hotels link internally') and clarifies the return value structure ('normalized best overall and best direct-booking prices'), helping the agent understand data provenance and processing logic.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two efficiently structured sentences with zero redundancy. The first sentence front-loads the action and required inputs, while the second explains internal resolution and output format. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and comprehensive annotations, the description adequately covers the tool's purpose, data source (Google Hotels), and return value types. It appropriately avoids duplicating return value details already present in the output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the baseline is 3. The description categorizes parameters into 'hotel name, city, dates, and optional guest/address fields' which provides logical grouping, but does not add semantic meaning, validation rules, or format details beyond what the schema already documents.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool 'Get hotel prices for an exact hotel stay' with specific inputs (hotel name, city, dates) and distinguishes its scope as targeting a specific property rather than browsing. With no sibling tools present, no differentiation from alternatives is required.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'for an exact hotel stay' provides clear context that this tool requires specific hotel identifiers and is not for broad destination searches. While it lacks explicit 'when not to use' language, the scope constraint effectively guides appropriate usage given the absence of sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!