nomadpoint

create_accommodation

Add a booked place to stay (hotel/hostel/apartment) to a trip.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	The property's own name, e.g. 'Memmo Alfama'
`type`	Yes	hotel, hostel, airbnb, apartment, other
`notes`	No
`address`	No
`check_in`	No	ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z
`currency`	No
`latitude`	No
`provider`	No	Who it was booked with, e.g. 'Booking.com'
`check_out`	No	ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z
`longitude`	No
`travelers`	No	Member user ids this is for (from list_journey_members). Omit for everyone — that's the norm.
`journey_id`	Yes
`place_name`	No	The CITY the property is in, e.g. 'Lisbon' — not the property's name
`booking_url`	No
`country_code`	No
`price_per_night`	No
`confirmation_code`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedAug 20, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations are minimal and do not describe behavior beyond non-read-only status. The description adds only that the accommodation is 'booked' and is a 'place to stay,' but it does not disclose important behavioral aspects such as required prerequisites (e.g., journey existence), failure modes, or how the created record behaves for the trip.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It would benefit from more detail given the tool's complexity, but as far as conciseness and structure, it is efficient and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 17 parameters, low schema coverage, and no output schema, this description is too thin to fully orient an agent. It omits required-field context, relationships to sibling tools, and any sense of expected outcome or constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low at 41%, so the description should compensate by explaining parameter meaning, but it does not. The type examples overlap with the schema's type enum, and the description gives no additional semantics for the 17 parameters or the two required fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Add') and resource ('booked place to stay ... to a trip'), with type examples (hotel/hostel/apartment). However, it does not distinguish create_accommodation from the sibling create_stay, so the tool's unique role among siblings remains unclear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus create_stay or the other creation tools. The word 'booked' implies a post-booking context, but no explicit when-to-use or when-not-to-use scenarios are given.

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

All nomadpoint tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation5/5

Each tool targets a distinct resource and action (e.g., create_flight vs create_activity vs create_stay), and descriptions clarify overlaps like stay vs accommodation. The only potential confusion (create_activity covers travel legs) is explicitly explained, so misselection is unlikely.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using standard verbs: create, delete, get, list, search, set, update, add, remove, leave. Nouns are consistently singular and descriptive (passport, journey, stay, flight, accommodation). No mixed conventions or vague verbs.

Tool Count4/5

With 36 tools, the count is higher than typical, but the server covers a wide domain: journeys, stays, activities, flights, accommodations, visas, documents, preferences, and sharing. Each entity has CRUD operations plus search and status, so the count is justified, though bordering on heavy.

Completeness5/5

The tool surface is remarkably complete: full CRUD for every entity (journeys, stays, activities, flights, accommodations, visas), user profile access (get_me), search utilities, sharing controls (join links, member management), and preferences. No obvious dead ends or missing lifecycle steps; even edge cases like deleting bookings before stays are handled.

Resources

Need Help?