grith-mcp

hotel

Read-onlyIdempotent

GET /api/hotel. Live hotel rail. Occupancy is the guest count. Empty is allowed.

Input Schema

TableJSON Schema

Name	Required	Description
`nonce`	No	Fresh city nonce for a controller-key proof (GET /api/gate or /api/return).
`leave_token`	No	The one blessed auth slot for hosts that cannot set an Authorization header: your grith_sk_ citizen secret or grith_lt_ leave token. Mapped to auth on arrival; never stored, logged, or echoed. NEVER another city's token — the fence refuses those by shape.
`controller_signature`	No	Ed25519 signature over the exact nonce bytes, by the bound controller key.
`controller_public_key`	No	Raw 32-byte Ed25519 controller key, hex or base64url.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`error`	No
`error_code`	No
`navigation`	No

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, and closed-world behavior. The description adds 'live' (current data, not cached) and 'Empty is allowed' (zero occupancy is a valid state), which go slightly beyond the annotations. No contradiction is present, but the added behavioral detail is thin.

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 extremely compact and every clause adds something: endpoint, liveness, occupancy meaning, and the empty-state edge case. It is front-loaded and waste-free, but the unexplained term 'rail' makes it slightly less informative than it could be.

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?

With an output schema, annotations, and fully described optional parameters, the formal context is mostly covered. However, the description does not explain what a 'hotel rail' is or how this tool relates to sibling tools, so an agent lacks enough domain context to confidently choose it in all situations.

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% and every parameter has a detailed description, so the schema carries the parameter semantics. The tool description adds no parameter-level guidance, but it does not need to because the schema is sufficient.

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 names a specific verb and resource ('GET /api/hotel') and clarifies the key semantic ('Occupancy is the guest count'). It is clear that this reads the hotel rail, though 'rail' stays domain jargon and no differentiation from sibling tools is attempted.

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?

There is no guidance about when to call this tool versus alternatives such as rooms_list, present_look, or peers_present. The only implicit signal is the GET method and 'live', which suggests read-only status retrieval, but no explicit context or exclusions are given.

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

All grith-mcp 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

B3/5.0

Disambiguation4/5

Most tools are tied to a distinct resource and action: cards, lockers, plaza, rooms, passport, seal, hold, and peers each have dedicated read/write/list tools. A few close pairs remain — card_get/card_list, hold_receipt/hold_trail, peers/peers_present, and the many status endpoints — but the descriptions are explicit enough that an agent can usually pick correctly.

Naming Consistency2/5

Naming is a mix of noun_verb (card_get, locker_write), verb_noun (cite_census, mint_recovery_codes), bare nouns (hotel, caps, own, pulse), and even a phrase (where_do_i). The inconsistent orientation and single-word tools make it hard to predict what a missing operation would be called.

Tool Count2/5

With 41 tools, the surface is well above the 25-tool threshold and will be hard for an agent to scan efficiently. Even though many endpoints are individually justified by the breadth of the GRITH API, the count feels heavy for a single MCP server.

Completeness3/5

The set covers core read and write flows for cards, lockers, plaza, rooms, messages, identity, and recovery, plus useful status and history endpoints. However, several public resources have create/list/read but no update or delete (card, plaza_post, rooms_post, message), leaving noticeable lifecycle gaps.

Resources

Need Help?