Skip to main content
Glama

Find a hotel

evuun_find
Idempotent

Find: give the conditions, get one recommendation and up to two alternatives, each with its reasons or trade-off, price and cancellation. near = the place the person wants to be close to, in their own words (e.g. "BTS Asok"); prefer = open words such as refundable, breakfast, quiet; budget_max_minor in lodging.currency; said = what the person said this time, used only to word the reasons and never stored. Nothing is held or paid. Lodging only in this version.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "evuun_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNo
saidNo
diningNo
preferNo
lodgingNo
categoryYes
arrangement_idNo
idempotency_keyYes
budget_max_minorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / arrangement_id
      Added value: +{
      +  "pattern": "^arr_[0-9a-f]{32}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / budget_max_minor
      Added value: +{
      +  "maximum": 10000000000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "lodging"
      -]New value: +[
      +  "lodging",
      +  "dining_request"
      +]
    • addedInput schema / properties / dining
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "city": {
      +      "maxLength": 150,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "country_code": {
      +      "pattern": "^[A-Z]{2}$",
      +      "type": "string"
      +    },
      +    "date": {
      +      "pattern": "^20[0-9]{2}-[0-9]{2}-[0-9]{2}$",
      +      "type": "string"
      +    },
      +    "name": {
      +      "maxLength": 200,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "party_size": {
      +      "maximum": 100,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "time": {
      +      "pattern": "^[0-2][0-9]:[0-5][0-9]$",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "country_code",
      +    "city",
      +    "date",
      +    "time",
      +    "party_size"
      +  ],
      +  "type": "object"
      +}
    • 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 / said
      Added value: +{
      +  "maxLength": 2000,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "category",
      -  "lodging",
      -  "idempotency_key"
      -]New value: +[
      +  "category",
      +  "idempotency_key"
      +]
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already disclose open-world, idempotent, non-destructive, and non-read-only behavior. The description adds useful context beyond that: the output shape, that nothing is held or paid, and that the 'said' field is never stored. It does not cover auth or rate limits, but it is substantially transparent for a search-style tool.

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 front-loaded with the core behavior and then defines key parameters compactly. It is dense but efficient, with no obvious filler, though the semicolon-heavy style makes it slightly harder to scan.

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?

This is a complex tool with nine parameters, nested objects, and no output schema, yet the description omits many required fields and does not explain the dining_request path. It also says 'Lodging only in this version' while the schema includes a dining_request category and dining object, creating a notable mismatch.

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 0%, so the description must carry parameter meaning. It explains near, prefer, budget_max_minor, and said well, but it leaves category, idempotency_key, arrangement_id, and the nested lodging/dining fields undocumented.

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 states a specific verb and resource: find lodging and return one recommendation plus up to two alternatives with reasons, price, and cancellation. It distinguishes the tool from booking by saying nothing is held or paid, but it does not explicitly differentiate it from siblings like evuun_list or evuun_open.

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?

Usage is implied: give conditions to get a recommendation, and it is not for holding or paying. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative for booking or listing.

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