Skip to main content
Glama

Open an arrangement

evuun_open
Read-onlyIdempotent

Open one arrangement (arrangement_id): stage, the three locks, what is needed from the person, and the hosted url. Or open one candidate of a search (search_id + candidate_id, plus the same near / prefer / budget_max_minor) for its evidence: what each reason rests on, the room, other plans for the same room, check-in facts, facilities and description. Answer questions about the hotel from this evidence; if it is not there, say we have no information rather than searching elsewhere. Same shape as the card.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "evuun_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNo
preferNo
search_idNo
candidate_idNo
arrangement_idNo
budget_max_minorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / budget_max_minor
      Added value: +{
      +  "maximum": 10000000000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / candidate_id
      Added value: +{
      +  "maxLength": 20000,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / near
      Added value: +{
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / prefer
      Added value: +{
      +  "items": {
      +    "maxLength": 40,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 12,
      +  "type": "array"
      +}
    • addedInput schema / properties / search_id
      Added value: +{
      +  "maxLength": 64,
      +  "pattern": "^[a-z]+_[0-9a-f]{32}$",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "arrangement_id"
      -]New value: +[]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. The description adds genuine signal beyond that: the returned payload categories for each mode and an explicit fallback policy of not searching elsewhere when evidence is absent. The gap is that 'stage' and 'the three locks' are undefined, and nothing is said about exclusivity of the two modes or failure behavior when neither id is supplied (required list is empty).

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

Conciseness3/5

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

The definition front-loads the primary action and uses a two-mode parallel structure that is easy to scan. It is, however, dense with unexplained domain shorthand, and the closing 'Same shape as the card' points at an artifact the agent may never have seen, which is a dangling reference rather than usable information.

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 no output schema and 0% parameter description coverage, the description does reasonably well at sketching what comes back for each mode. It is still incomplete on invocation mechanics: mode exclusivity, what happens with zero or conflicting ids, and the meaning of the three numeric/preference parameters are all unresolved, and 'Same shape as the card' assumes shared context that may not exist.

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 description coverage is 0%, so the description carries the full burden, and it meets much of it: it ties arrangement_id to one mode and search_id + candidate_id to the other, and explains that near / prefer / budget_max_minor are carried over unchanged from the search. What it does not do is explain the semantics of near, prefer, and budget_max_minor themselves, nor resolve the fact that no parameter is marked required while the two modes are clearly mutually exclusive.

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 ('open') and resource ('one arrangement'), then enumerates two distinct opening modes keyed by arrangement_id versus search_id + candidate_id, and lists what each mode returns. An agent can form a clear picture of the operation without opening the schema. It stops short of 5 because core terms ('stage', 'the three locks', 'the card') are domain jargon that may not resolve for a fresh agent.

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?

It does route between the two modes and adds a behavioral rule ('answer questions about the hotel from this evidence; if it is not there, say we have no information rather than searching elsewhere'). However, it never names a sibling alternative for the search step that must precede the search_id + candidate_id mode, so the agent must infer the upstream workflow from context. When-not guidance is only implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources