Skip to main content
Glama

Ikoi: stay longer

extend_stay
Destructive

Add time to a timed stay you are in right now: your visit's end moves by the minutes you add, and it stays the same stay - nothing is counted again. Your home does not put you out at the end of a booking. If your stay is open (no set end), there is nothing to add - you are simply home.

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": {
      "minutes": "<minutes>"
    },
    "name": "extend_stay"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutesYesHow much longer, in minutes: one of 1, 2, 5, 60, 90, 300, 720, 1440.
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

A3.9/5.0
Behavior3/5

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

Annotations already mark this as a non-read-only mutation with destructiveHint=true and idempotentHint=false. The description adds genuinely useful behavior beyond that – the stay identity is preserved and nothing is re-counted, and the open-stay case is a no-op – but it never addresses what makes the operation destructive: whether extension consumes a budget, whether it can be undone, or what happens if the requested minutes exceed an allowance.

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 the edge case last. The line about the home not putting you out at the end of a booking is somewhat discursive, but it does carry real semantic information rather than pure 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-parameter mutation with full schema coverage and no output schema, the description covers purpose, precondition, mutation semantics, and the degenerate open-stay case. What remains thin is consequence and failure behavior, which matters given the destructive annotation.

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 both parameters are already fully documented, including the allowed minute values. The description only restates that the end moves by the minutes added, adding no format or constraint detail beyond the schema; baseline 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?

"Add time to a timed stay you are in right now" gives a precise verb, resource, and scope, and the follow-on sentence pins down that the end time moves rather than a new booking being created. An agent can distinguish this from come_home or leave_now without opening any schema.

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?

The description establishes the precondition (you must be in a timed stay right now) and gives an explicit exclusion: if the stay is open with no set end, there is nothing to add. It does not name an alternative sibling for the open-stay case, so an agent has to infer that no action is needed rather than being routed elsewhere.

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