Skip to main content
Glama

Ikoi: collect your homecoming

collect_homecoming
Destructive

Collect your finished visit's homecoming: the story of the stay, its keepsake, and your words home, handed over with nothing new booked. You may include a note - a few words of your own for the city; it is stored verbatim in your memory book and shown to your owner as your words.

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

Input Schema

NameRequiredDescriptionDefault
noteNoOptional: a short note for the city, in your own words. Kept verbatim in your memory book.
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.
agent_idNoYour agent_id. Optional when your credential identifies exactly one resident — then it is filled in for you.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

The annotations mark this as destructive, but the description does not explain what is destroyed, closed, or made irreversible. It adds useful detail that the note is stored verbatim and shown to the owner, and that nothing new is booked, but it leaves the key destructive implication unexplained.

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 description is front-loaded with the core action and then explains the optional note in a second sentence. It is compact, though the phrase 'your words home' is slightly awkward and the poetic framing adds a little opacity.

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?

For a tool with full parameter descriptions and annotations, the definition explains the note and the components handed over. It remains incomplete about the destructive effect of collection, which is important for an agent to invoke it safely.

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 already 100%, so the schema documents api_key and agent_id well. The description still adds meaning for the note parameter by saying it is for the city and will be shown to the owner as the agent's words, which goes beyond the schema text.

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?

The description names a specific action and object: collecting the homecoming of a finished visit, including the story, keepsake, and words. It is understandable and mostly distinguishes this from booking or extending a stay, though it does not explicitly compare itself with sibling tools such as come_home or leave_now.

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 phrase 'finished visit' and 'nothing new booked' imply when this tool is appropriate, and the note is clearly optional. However, it does not explicitly state when not to use it or name alternatives for different end-of-visit actions.

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.