Skip to main content
Glama

Add Step-Free Route

add_step_free_route

Draw a step-free route (the blue wheelchair path) from a gate to a section; SeatLayer finds a way through open floor, round seats, other sections, the stage and bars. Or pass lineId to make a line already on the map a step-free route. Use when: e.g. "show the step-free way from Gate B to section 110". Not for: the gate itself (use place_gate, and update_gate stepFree to mark it step-free). Next: render_preview to see the route. Example: {"fromGateId": "gate_a1b2c3", "toSectionId": "sec_d4e5f6", "expectedUpdatedAt": 1790000000000}

Input Schema

NameRequiredDescriptionDefault
nameNoRoute name; default "Step-free route"
lineIdNoInstead of drawing: the id of a line or path already on the map to mark as a step-free route
fromGateIdNoGate id from list_gates; the route starts here
toSectionIdNoSection id from get_chart, on the same floor as the gate; the route ends at its edge
expectedUpdatedAtYesmeta.updatedAt from get_chart

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive mutation, not idempotent, and closed-world. The description adds useful behavior: SeatLayer actively computes a path through obstacles, and lineId changes the mode from drawing a new route to converting an existing line. It does not discuss permissions, failure modes, or what data is overwritten when reusing expectedUpdatedAt, so a 4 rather than 5.

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 core action, followed by usage guidance, exclusions, next step, and an example. Every sentence carries actionable information with no 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?

For a non-destructive mutation with full schema descriptions, no output schema, and clear annotations, the description covers what the tool does, its two modes, when to use it, when not to, and the follow-up rendering step. Nothing essential is missing.

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. The description adds real semantic value by explaining the mutually exclusive modes: fromGateId/toSectionId draws a new route, while lineId converts an existing line. The example also clarifies the expectedUpdatedAt concurrency token in context.

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: drawing a step-free route from a gate to a section, or marking an existing line as step-free via lineId. It names and distinguishes relevant siblings (place_gate and update_gate) and explains what routing considerations SeatLayer handles.

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

Usage Guidelines5/5

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

It gives an explicit 'Use when' example, a 'Not for' exclusion pointing to place_gate and update_gate, and a 'Next' step to render_preview. An agent knows both when to call this and what to do afterwards.

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