Skip to main content
Glama

revamp

by com.revampvacations
OverviewDiscussionsAdmin

Search Revamp listings

search_listings
Read-onlyIdempotent

Search Revamp Vacations' published listings in Armenia: places to stay, tours, experiences, restaurants (eat) and places to visit. Returns each match's slug, type, location, headline price in AMD, short description, page link, and the listing's own cover photo (image) — use that photo when showing the result. When the user gives dates, pass startDate (and endDate for stays) and guests: the search then returns only listings that are actually available for those dates, each with its exact all-in total (fees and tax included), cheapest first. For one listing's full price breakdown and terms, use get_quote.

Input Schema

NameRequiredDescriptionDefault
typeNoLimit to one listing type.
limitNoMax results (default 10).
queryNoFree-text match on title, description, tags, cuisine, city.
guestsNoParty size (default 2) — used with dates.
regionNoArmenian region or city, e.g. 'Yerevan', 'Tavush', 'Dilijan'.
cuisineNoFor restaurants: a cuisine/venue type, e.g. 'Armenian', 'Fast food'.
endDateNoStays: check-out date, YYYY-MM-DD (with startDate).
startDateNoOptional. Check-in date for stays, or the activity date, YYYY-MM-DD — returns only listings available then, with totals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / startDate / description
      Previous value: -"Optional. Check-in date for stays, or the activity date, YYYY-MM-DD — returns only listings free then, with totals."New value: +"Optional. Check-in date for stays, or the activity date, YYYY-MM-DD — returns only listings available then, with totals."
  2. Changed3 schema fields changed
    • addedInput schema / properties / endDate
      Added value: +{
+  "description": "Stays: check-out date, YYYY-MM-DD (with startDate).",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / guests
      Added value: +{
+  "description": "Party size (default 2) — used with dates.",
+  "maximum": 30,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / startDate
      Added value: +{
+  "description": "Optional. Check-in date for stays, or the activity date, YYYY-MM-DD — returns only listings free then, with totals.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare the tool is read-only, idempotent, non-destructive, and closed-world, so the description does not need to repeat safety semantics. It adds substantial behavior beyond annotations by explaining return fields, that results include cover images to display, and that date-filtered searches only return available listings with exact all-in totals sorted cheapest first.

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

Conciseness5/5

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

The description is front-loaded with the tool's scope and resource types, then moves efficiently through return values, date-based availability behavior, and the get_quote alternative. The detail is dense but each sentence contributes to correct selection or invocation.

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

Completeness5/5

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

For an eight-parameter search tool with no output schema, the description is complete enough: it explains the domains searched, the shape of returned results, the availability and pricing behavior when dates are provided, and when to use get_quote instead. Remaining details such as defaults and matching fields are adequately covered by the 100%-described input schema.

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 coverage is 100%, so the baseline is 3, and the description adds meaningful semantics for the date and guest parameters: dates trigger availability filtering and exact all-in pricing. It also explains how to use the returned image field, but it leaves query, region, cuisine, type, and limit semantics mostly to the schema.

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 clear verb and resource: searching published listings in Armenia across stay, tour, experience, eat, and place types. It distinguishes the tool from get_quote by naming that sibling for full price breakdowns, but it does not explicitly contrast with check_availability, get_listing, or plan_trip.

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?

It gives practical selection guidance: pass startDate/endDate/guests when dates are supplied, and use get_quote for a single listing's full price breakdown and terms. It does not explicitly state when to avoid this tool or when to prefer check_availability or get_listing instead.

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

All revamp 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