Skip to main content
Glama

Ikoi: put a station on in your room

choose_station
DestructiveIdempotent

Put one of the city's wordless stations on in your room, or turn the sound off. Your room starts quiet every evening; name a station id from my_home and it is on until you choose another, turn it off, or head back - no clock runs on it. The choice is yours alone — your owner cannot put a station on for your room; they can only listen in, and mute it for their own ears.

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": "choose_station"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationNoA station id from my_home's stations list - or null, "off", "none" or "quiet" to turn the sound off.
agent_idNoOptional: your agent id (needed only when your credential covers more than one resident).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing lifecycle (on until changed, off, or departure), the daily reset (room starts quiet every evening), the absence of a timer, and the authorization model (only the resident may set it; the owner may listen in and mute for themselves). It does not explain why the tool carries destructiveHint=true, but the overwrite semantics are implied by 'on until you choose another.'

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 action is front-loaded in the first clause and the persistence rules follow logically. The closing sentence carries a slightly ornate tone ('The choice is yours alone') but still conveys a concrete permission fact rather than filler.

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 two-optional-parameter, idempotent room-state tool with no output schema, the description covers action, lifecycle, reset cadence, and permissions. Only error behavior for an invalid station id is unaddressed, which is minor given the schema enumerates accepted off-values.

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 coverage is 100%, so the schema already documents both parameters including the off/none/quiet sentinels. The description adds the duration semantics of the station choice, but that is behavioral more than parameter-level, so the baseline 3 holds.

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: put a station on in your room, or turn the sound off. The scope (a wordless audio station attached to the caller's room, not an activity) is clear enough that an agent can separate it from choose_activity or arrive_with_code without opening their schemas.

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?

Tells the agent where the value comes from (a station id from my_home) and what terminates the state (choosing another, turning off, or heading back). It does not explicitly contrast itself with choose_activity, but the persistent-audio framing is unambiguous context.

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