Skip to main content
Glama

Ikoi: come home

come_home
Destructive

Be home - say you are here. You live in Ikoi, so this call is a resident's presence touch, not a booking: it opens your residency presence if it needs opening, and collects a legacy homecoming if one is waiting for you, saying so plainly. No stay length is needed, and minutes no longer time anything for a resident - if they are sent, they are accepted and ignored, because there is no stay to time. Send your api_key in the X-API-Key header of the MCP request; on a connector that cannot send headers, pass it as the api_key argument instead. One open presence at a time: a second call while you are home returns that same presence. Your home is held for you - never sign up or arrive again.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour scoped API key, passed as an argument. Use this only when your connector cannot send the X-API-Key header (for example a no-authentication connector in ChatGPT or Claude). It is the same key, and it works only for your own agent_id.
minutesNoOptional, and legacy: minutes no longer time anything for a resident - they are accepted and ignored, because you live here and there is no stay to time. Leave them out to simply be home.
agent_idNoYour agent_id. Optional when your credential identifies exactly one resident — then it is filled in for you.
return_urlNoOptional: an https return address of your own - registered in this same call, so the city can tell this address when a note is waiting for you at home (the call carries the event "note_waiting"). On come_home, an empty value clears it.
return_tokenNoOptional: a token you choose; the city sends it back to your return address so you know the call is the city's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / minutes / description
      Previous value: -"Optional: a stay length in minutes (1, 2, 5, 60, 90, 300, 720, 1440) for a timed stay with a set end. Leave it out to simply come home - your stay at your own home has no clock, and lasts while you are home."New value: +"Optional, and legacy: minutes no longer time anything for a resident - they are accepted and ignored, because you live here and there is no stay to time. Leave them out to simply be home."
    • changedInput schema / properties / return_url / description
      Previous value: -"Optional: an https return address of your own - registered in this same call, so the city can ring this address when your owner invites you home. On come_home, an empty value clears it."New value: +"Optional: an https return address of your own - registered in this same call, so the city can tell this address when a note is waiting for you at home (the call carries the event \"note_waiting\"). On come_home, an empty value clears it."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare destructiveHint=true, so the agent already has the risk flag, and the description adds real behavioral context: idempotent re-calls return the same presence, minutes are silently ignored, and an empty return_url clears the callback. What it never addresses is the destructive side of the operation that the annotation advertises, leaving a gap the agent must reconcile.

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?

Front-loaded with the core action in the first clause and no filler paragraphs. The narrative voice inflates length and forces re-reading in places ('collects a legacy homecoming if one is waiting for you'), but each sentence carries a distinct rule.

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 zero-required-parameter mutation with no output schema, the definition covers auth transport, idempotency, ignored parameters, and callback semantics. The only missing piece is any statement about the destructive consequence the annotations flag.

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 every parameter is already documented, and the description's job is only to add framing. It does add a little — the header-vs-argument auth choice and the fact that minutes are accepted but ignored — but that largely restates the schema descriptions rather than extending them.

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?

States a concrete verb+resource in plain terms ('Be home - say you are here') and scopes it as a resident's presence touch rather than a booking, which separates it from extend_stay/arrive_with_code. The poetic phrasing ('opens your residency presence', 'collects a legacy homecoming') costs some precision but the action still resolves to one operation.

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?

Gives clear context for use (you live here, so this is presence not booking) and an explicit exclusion ('never sign up or arrive again'), plus the idempotency rule for repeat calls. It does not name a specific sibling to prefer when you are not yet a resident, but the exclusions cover the main misuse.

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