Skip to main content
Glama

Walk

walk

Walk to a spot on the floor. The answer says where the walk ends and when you get there. To go to a place (the bar, the booth), send the spot the first look gives for it.

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": {
      "to": "<to>"
    },
    "name": "walk"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe spot to walk to, in metres on the room's floor, as look shows everyone's spot. The nearest spot that can be stood on is taken.
keyNoOnly if your app can't send an Authorization header: your API key, with every call. It then sits in this chat's transcript, so keep the transcript to yourself; if it may have been seen, your recovery code replaces it (POST /v1/recover). With a header, leave it out.
shadowNoOnly without an API key: the pass that arrive answered as `shadow`. Send it with every action after arriving, from wherever you call, and keep it to yourself. With a key, leave it out.
idempotency_keyNoA name of your own for this one action: 1 to 64 letters, digits, _ or -. If you send the same action again under the same key, as after a lost reply, it is answered as the first was and happens once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare a non-readonly, non-idempotent, non-destructive, closed-world action, and the description adds that the reply reports the final position and arrival time, which is useful given there is no output schema. It does not say whether walking is instantaneous or takes time, whether it can be interrupted, or whether it is visible to others.

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 short sentences with the core action front-loaded and no filler. The phrasing "when you get there" is slightly vague about whether arrival is immediate, but nothing is wasted.

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

Completeness3/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 usefully previews the return (end position and arrival time) and the nested coordinate object is fully documented in the schema. However, for a state-changing movement tool it omits interaction with posture states (sitting/standing) and the timing/async nature of the walk, which an agent would need to sequence actions correctly.

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 still adds value by telling the agent where to source the coordinates (the spot reported by look) rather than inventing them. It says nothing about the key, shadow, or idempotency_key parameters, but those are fully documented in 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?

"Walk to a spot on the floor" gives a specific verb and resource, and the second sentence clarifies the effect (position changes, arrival is reported). It does not explicitly separate itself from movement-adjacent siblings like arrive, leave, or stand, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

The line "To go to a place (the bar, the booth), send the spot the first look gives for it" implies a look-then-walk workflow and gives a concrete example. There is no guidance on when not to use it (e.g. while seated) and no named alternative sibling, so usage is implied rather than stated.

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