Skip to main content
Glama

travel

by ai.autonomad
OverviewDiscussionsAdmin

search_dining

Read-onlyIdempotent

Searches restaurants in a city for a date, with optional time, party size, cuisine, price range and neighborhood. For planning only: it returns restaurant details and indicative availability. Autonomad does not place restaurant reservations; any booking is made with the restaurant directly.

Input Schema

NameRequiredDescriptionDefault
cityYes
dateYesYYYY-MM-DD
timeNoHH:MM in 24h
placeNoThe exact place of this trip stop: the `place` an earlier search for the trip returned, or the candidate the person picked when a search asked which place they meant. Searches given the same place cover the same place.
cuisineNo
party_sizeNo
price_rangeNo
neighborhoodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / place / properties / arrival_airports
      Added value: +{
+  "description": "The airports to fly this place by, best first, as a search returned them. Pass them back unchanged.",
+  "items": {
+    "properties": {
+      "iata": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "iata"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / place / properties / extent_km
      Added value: +{
+  "description": "The size of a region or island, as a search returned it.",
+  "type": "number"
+}
    • addedInput schema / properties / place / properties / gateway_airport
      Added value: +{
+  "description": "The one airport a wide search flies this place by, as a search returned it.",
+  "type": "string"
+}
    • addedInput schema / properties / place / properties / kind
      Added value: +{
+  "description": "What the place is, as a search returned it. Pass it back unchanged: a town, region or island has its hotels searched around it.",
+  "enum": [
+    "city",
+    "town",
+    "region",
+    "island"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / place / properties / radius_km
      Added value: +{
+  "description": "The hotel search radius for this place, as a search returned it.",
+  "type": "number"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / place
      Added value: +{
+  "description": "The exact place of this trip stop: the `place` an earlier search for the trip returned, or the candidate the person picked when a search asked which place they meant. Searches given the same place cover the same place.",
+  "properties": {
+    "airports": {
+      "description": "IATA codes of the airports serving the place.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "city": {
+      "type": "string"
+    },
+    "country": {
+      "description": "ISO 3166-1 alpha-2 code (territories use their own, e.g. PR).",
+      "type": "string"
+    },
+    "label": {
+      "description": "How to name the place to the person, e.g. 'Birmingham, GB'.",
+      "type": "string"
+    },
+    "latitude": {
+      "type": "number"
+    },
+    "longitude": {
+      "type": "number"
+    },
+    "region": {
+      "description": "State or region, or empty.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "country",
+    "latitude",
+    "longitude"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are "indicative availability" and no reservation is placed, which sets correct expectations about the response. It omits pagination/result-count behavior, keeping it at 4.

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?

Three sentences, front-loaded with the core action, and the caveat is short and purposeful. Slightly compressed phrasing ("in a city for a date") costs a bit of readability but nothing is wasted.

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

Completeness4/5

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

For an 8-parameter, nested-object tool with no output schema, the description gives the essential frame: what is searched, what is returned (details plus indicative availability), and what is not done (no booking). Missing only secondary detail such as result limits or how the nested `place` interacts with `city`, which keeps it below 5.

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 only 38%, and the description compensates partially by enumerating the available filters (time, party size, cuisine, price range, neighborhood). However, it adds no format or semantics for the undocumented params (city, cuisine, party_size, price_range, neighborhood), so the low-coverage gap is not fully closed.

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?

States a specific verb and resource ("Searches restaurants in a city for a date") plus the full set of optional filters. The resource distinguishes it immediately from siblings like search_hotels, search_activities and search_events without needing to open any schema.

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

Usage Guidelines4/5

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

Explicitly frames the tool as planning-only and rules out a booking capability ("Autonomad does not place restaurant reservations; any booking is made with the restaurant directly"), which prevents a whole class of misuse. It stops short of naming alternatives (e.g. search_hotels/search_events) for adjacent intents, so it lands at 4 rather than 5.

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

All travel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources