Skip to main content
Glama

aamio_close_channel

DestructiveIdempotent

Closes a channel before it expires, deleting the thread and blocking future receipts. Notify writers first, because the address stays active and new messages become unread.

Instructions

Close a channel before it expires. The thread is deleted with what was written on it, and no receipt can be taken afterwards. The address is not closed: whoever still holds it can write there afterwards, which opens a new thread with no list and no gate, the writer is answered that it was stored, and nobody reads it. So tell whoever writes there before closing. The answer says whether the service deleted it and whether it left this home: when the service does not say the thread is gone, the channel is kept and still read, so nothing written there is lost unseen.

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": {
      "label": "<label>"
    },
    "name": "aamio_close_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYesthe channel's label, as aamio_channels shows it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.36
    • addedInput schema / properties / label / description
      Added value: +"the channel's label, as aamio_channels shows it"
  2. First observedv0.5.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds substantial context beyond them: the thread and its contents are deleted, no receipt can be taken afterwards, and the address stays writable so later messages go unread. It also explains the response semantics (whether the service deleted it and whether it left this home) and the fallback when deletion is not confirmed. The only gap is that it does not state permission or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The destructive consequence is front-loaded, which is good, but the prose is dense and run-on, with several clauses chained by commas that slow parsing. Every sentence carries real information, yet the same points could be made in fewer, shorter sentences.

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?

With no output schema, the description compensates by explaining what the answer reports and what happens when the service does not confirm deletion. Combined with the destructive/idempotent annotations, an agent has enough to call this safely; only permission requirements are unaddressed.

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% for the single 'label' parameter, and the schema already says it is the label as aamio_channels shows it. The description adds no further meaning about the label format or matching rules, so the baseline 3 applies.

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 specific verb and resource ('Close a channel before it expires') and immediately clarifies the scope of the close (thread deleted, address remains open). It is clearly distinguishable from aamio_open_channel, though it never names a sibling explicitly.

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?

Gives a strong operational precondition ('tell whoever writes there before closing') but does not frame when to choose this over alternatives such as letting a channel expire or using aamio_open_channel. Usage is implied rather than routed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.