Skip to main content
Glama

Can the smart glasses rental be booked automatically?

check_glasses_rental
Read-only

Checks MDJ's rules for an AI agent booking the smart glasses rental (voice guide MAYA) by itself: the destination must be approved, the kit handover must be at an approved place (secure locker at Ben Gurion airport, or courier delivery in central Israel), the start date must be at least 30 days away, and a kit must be free for the dates. When all pass, returns the price from the MDJ store, the checkout link and a signed AP2-style cart. When any fails, returns how the traveler contacts MDJ: Maya answers those requests case by case. Never creates a booking.

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": {
      "destination": "<destination>",
      "start_date": "<start_date>",
      "end_date": "<end_date>",
      "handover": "<handover>"
    },
    "name": "check_glasses_rental"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageNoOptional, default smart-trip. smart-trip: the traveler planned the route. mdj-planner: Maya also plans the route. vip-experience: planning plus eSIM, video editing and home delivery.
end_dateYesLast day of the rental, YYYY-MM-DD.
handoverYesairport_locker: secure locker at Ben Gurion airport. home_delivery: courier to the traveler's address.
start_dateYesFirst day of the rental, YYYY-MM-DD.
destinationYesCountry or city of the trip, for example "Vietnam" or "Hoi An".
delivery_areaNoRequired for home_delivery: is the address in central Israel?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, but the description adds substantial behavior: the exact rule set evaluated, the success payload (store price, checkout link, signed AP2-style cart), and the failure path (traveler is directed to Maya who handles it case by case). It also explicitly disclaims any write effect, removing ambiguity for a mutation-adjacent workflow.

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 rules are front-loaded in a parallel must/must/must structure, and the success and failure outcomes follow immediately. The opening sentence is long and packs four conditions into one sentence, which is dense but not wasteful; no sentence is filler.

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?

With no output schema, the description must explain returns, and it does so for both branches (price/checkout link/signed cart vs. contact path). Required parameters, the conditional delivery_area, and the failure mode are all covered, leaving nothing an agent needs before calling.

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, but the description adds real semantics the schema lacks: destination must be 'approved', handover must be an approved location (locker at Ben Gurion or central-Israel courier), and start_date must be at least 30 days out. These business rules give the parameters decision weight beyond their enumerated values.

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?

The description states a specific verb and resource: it 'checks MDJ's rules for an AI agent booking the smart glasses rental' and enumerates the four conditions (destination approval, handover location, 30-day lead time, kit availability). This is clearly a read-only eligibility pre-check, distinguishable from siblings like check_destination_season or create_cart_mandate.

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 clear outcome-based context: call it to learn whether an automated booking can proceed, and it states 'Never creates a booking', implicitly routing creation elsewhere. It does not name the alternative tool to use for an actual booking or for the case-by-case Maya path, so it falls short of full when/when-not/alternatives guidance.

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