A
licenseA
qualityC
maintenanceMCP server providing cosiness scores for about 6,300 independent hotels, with tools to find hotels by city/country and retrieve detailed feeling data.
2
MIT
Got Cosy
Server Details
Travel/hotel data: 6,300 hotels scored for cosiness from guest reviews; verified booking links.
- 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.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.5/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool targets a distinct operation: searching for hotels vs. retrieving details for a specific hotel. No overlap in functionality.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern: 'find_cosy_hotels' and 'get_hotel_feeling'. While 'find' and 'get' are different, they are both common action verbs and the pattern is uniform.
Tool Count4/5
With only 2 tools, the set is minimal but appropriate for a niche service focused on accessing a cosiness index. It covers the core needs of searching and retrieving details without unnecessary bloat.
Completeness5/5
The tool set provides all necessary operations for the domain: searching with filters and retrieving detailed information by identifier. No obvious gaps as the service is read-only and focused on a single entity type.
Available Tools
2 toolsfind_cosy_hotelsAInspect
Find live, cosy-scored hotels from Got Cosy's cosiness index (gotcosy.com): hotels scored 0-10 for warmth, intimacy and character from photos and reviews. Only returns hotels that clear the public floor (score 5.0+). Optionally filter by city, country and a minimum cosy score.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | City name, e.g. "Paris" | |
| limit | No | Max results (default 20, max 100) | |
| country | No | Country name, e.g. "France" | |
| min_score | No | Minimum cosy score 0-10 (the public floor is 5.0 regardless of this value) |
Tool Definition Quality
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses that only hotels with score >=5.0 are returned, that min_score does not override the floor, and that data is 'live'. This provides important behavioral context beyond basic purpose.
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 concise sentences: first states main purpose and source, second lists optional filters. No wasted words, information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description does not specify what fields are returned for each hotel (e.g., name, location, score). While sufficient for a search tool, it lacks details about the result structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the description adds value by explaining the min_score parameter's interaction with the public floor ('the public floor is 5.0 regardless of this value'). This clarifies semantics beyond the schema's 'Minimum cosy score'.
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 clearly states the tool finds 'live, cosy-scored hotels' from a specific source, with a defined score range (0-10) and a floor of 5.0. It distinguishes itself from sibling tool 'get_hotel_feeling' by focusing on listing hotels rather than retrieving a single hotel's feeling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for searching hotels with optional filters but does not explicitly compare to sibling tool 'get_hotel_feeling' or specify when to use each. It mentions the public floor but lacks when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_hotel_feelingAInspect
Get one hotel's cosy score, evidence signals and description from Got Cosy, by its slug (as returned in find_cosy_hotels' results, or from a gotcosy.com/en/hotels/ URL). Below-floor hotels return {below_bar:true} with no score exposed.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The hotel's Got Cosy slug |
Tool Definition Quality
A4.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses special behavior for below-floor hotels. No annotations provided, so description carries burden. Could mention authentication or rate limits, but fine for a simple read operation.
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, no fluff. Front-loaded with purpose. Efficient and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, but description adequately covers return values (score, signals, description) and edge case. Complete for the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with one parameter described. Description adds value by explaining how to obtain the slug from find_cosy_hotels results or URL, beyond the schema's brief description.
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?
Clearly states verb 'get', resource 'one hotel's cosy score, evidence signals and description', and input 'slug'. Distinguishes from sibling tool 'find_cosy_hotels' by specifying slug source.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly mentions when to use (by slug from find_cosy_hotels or URL) and describes edge case (below-floor hotels return {below_bar:true}). Provides clear context for usage.
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!
Related MCP Servers
- Alicense-qualityBmaintenanceBook hotels worldwide — search, price, prebook & book across 249 countries. 65 tools for hotel search, flights, loyalty, analytics. Zero API keys needed. at best prices for hotels 3 M+ property91MIT
- Alicense-qualityCmaintenanceEnables verified, bookable hotel price checking with tax-inclusive totals, OTA tax status flags, and durable Booking.com fallback links for budget travel planning.MIT
- Alicense-qualityCmaintenanceLuxury hotel intelligence and secure checkout handoff for AI travel agents.1Apache 2.0