Skip to main content
Glama
Sign In

switch

by ai.switchapp
OverviewDiscussionsAdmin

Apply Travel

apply_travel
Read-onlyIdempotent

Luxury travel + hotel editorial. Real architecture is preserved exactly (no inventing buildings). Choose subject: hotel hero, rural property, scenic view, drone aerial, lifestyle moment, or interior. If you attach a reference image of a real property, the architecture lock kicks in automatically. Returns the styled prompt stack for your shot and the aspect_ratio to make it at — pair it with generate_image and pass that aspect_ratio along.

Input Schema

NameRequiredDescriptionDefault
styleYeshotel_hero = property is the star. rural_property = country estate. scenic_view = pure landscape. drone_aerial = top-down or 45° from above. lifestyle = model + destination. interior = inside the property.
subjectNoWhat you want to shoot. E.g. "a woman walking through a hotel lobby" or "morning coffee on the balcony".
aspect_ratioNoOptional frame shape. Replaces the shape the style uses by default. The answer carries aspect_ratio: pass it to generate_image so the picture is made at that shape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / aspect_ratio
      Added value: +{
+  "description": "Optional frame shape. Replaces the shape the style uses by default. The answer carries aspect_ratio: pass it to generate_image so the picture is made at that shape.",
+  "enum": [
+    "9:16",
+    "16:9",
+    "1:1",
+    "4:5",
+    "5:4",
+    "3:2",
+    "2:3",
+    "4:3"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent safety, and the description adds meaningful behavior: architecture is preserved exactly and reference images trigger an automatic architecture lock. It also discloses that the return is a prompt stack plus aspect_ratio, though it does not detail error cases or limits.

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 domain is front-loaded in the first sentence, and the description stays compact with no obvious padding. It is dense but every sentence carries relevant information about subject choice, reference-image behavior, and output usage.

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?

There is no output schema, but the description explains what is returned (styled prompt stack and aspect_ratio) and how to use it with generate_image. Combined with annotations and complete parameter documentation, an agent has enough to invoke it correctly, though a bit more on reference-image expectations could help.

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 100%, so the schema already documents all three parameters thoroughly, including enum meanings and aspect_ratio usage. The description's parameter-related content mostly repeats what is in the schema rather than adding new semantics.

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 establishes a clear domain ('Luxury travel + hotel editorial') and specific output ('styled prompt stack ... aspect_ratio'). It distinguishes itself from generic style siblings like apply_product or apply_wellness by naming the travel/hotel niche, though it does not explicitly call out those alternatives.

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 explicit workflow guidance ('pair it with generate_image and pass that aspect_ratio along') and conditions ('If you attach a reference image ... the architecture lock kicks in'). It lacks a direct when-not-to-use statement versus other style tools, but the travel/hotel context is clear.

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

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