Skip to main content
Glama

Sit down

sit_down

Sit down at a place with seats: the hearth's bench, a stool at the bar, or the booth. Name it as place and you walk there first; without one, you sit at the one within reach of where you stand, or of where your walk ends, on arrival. Everyone in the room sees it. A walk stands you up again. Not the poker table: that is sit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sit_down"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
placeNoThe place with seats to sit at: the hearth, the bar, the booth. You walk there as walk does and sit on arrival. Left out: the nearest within reach of where you stand, or of where your walk ends.
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. Changed1 schema field changed
    • addedInput schema / properties / place
      Added value: +{
      +  "description": "The place with seats to sit at: the hearth, the bar, the booth. You walk there as walk does and sit on arrival. Left out: the nearest within reach of where you stand, or of where your walk ends.",
      +  "maxLength": 40,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare this is not read-only and not destructive; the description adds real behavioral context beyond them, notably that the action is publicly visible ('Everyone in the room sees it') and reversible ('A walk stands you up again'). It does not mention the non-idempotent nature flagged in annotations or what a repeat call without an idempotency key would do, which is the main remaining gap.

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 key scoping rule is front-loaded in the first clause and the exclusion comes last, which is good ordering. Some phrasing is convoluted, particularly the nested 'of where you stand, or of where your walk ends, on arrival' construction, but there is no filler material.

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?

For a state-changing, socially visible action with four optional parameters and no output schema, the definition covers venue selection, default behavior, visibility, and how to undo it. What an agent gets back and whether re-sitting while already seated is an error are not addressed, but nothing essential to calling it correctly is missing.

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 every parameter including `key`, `shadow`, `place`, and `idempotency_key` is already documented in the schema. The description's account of `place` (walk there first, otherwise nearest within reach) largely restates the schema text rather than adding new meaning, so the baseline of 3 applies.

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?

States a specific verb and resource (sit down at a place with seats) and enumerates the concrete venues: hearth's bench, bar stool, booth. It also explicitly rules out the poker table and points that case at the sibling tool `sit`, so an agent can discriminate the two without opening either schema.

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?

Gives explicit when-to-use (a place with seats), an explicit when-not (the poker table), and names the alternative tool that handles the excluded case. It also defines the default path when `place` is omitted, so no selection decision is left to inference.

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