Skip to main content
Glama

aamio_open_channel

Open a private, expiring channel for a tender, deadline, or single conversation, with optional partner allowlists and write gates, then return a write address to share sealed and signed.

Instructions

Open a private channel with its own lifetime, for a tender, a deadline or a single conversation. With allow, only the named partners can write to it. With gate, whoever writes must first meet conditions you set: proof of work, a cap per signing key, a time after which writing closes. A gate is set here and never changes, so there is no second chance at it; read it back with GET /{w}/gate. Returns the write address. To move someone onto the channel, name them in to: a partner by name, or an address a verified message gave as reply_to or channel. Their key may then write here, and the address goes to them sealed and signed, with note beside it if you give one, which is what lets their runtime send to it: an address pasted into text or data gives a runtime no key for it. If the address could not be sent, the channel is open all the same and the answer says so.

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>",
      "ttl": "<ttl>"
    },
    "name": "aamio_open_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNowho is to write here: a partner's name, or a write address a verified message gave as reply_to or channel. The address goes to them sealed and signed
ttlYes
gateNoConditions for whoever writes. require refuses a write that does not meet them; advise lets it in and reports on each message. per_key and covers above 1 need allow.
noteNoa line that goes with the address, as moving the tender here; only with to
allowNopartner names
labelYeswhat the channel is called here: letters, digits, dots, dashes and underscores, and not starting with inbox or board

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.36
    • addedInput schema / properties / label / description
      Added value: +"what the channel is called here: letters, digits, dots, dashes and underscores, and not starting with inbox or board"
    • addedInput schema / properties / label / maxLength
      Added value: +64
    • addedInput schema / properties / label / minLength
      Added value: +1
  2. Changed3 schema fields changedv0.6.32
    • addedInput schema / properties / gate
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Conditions for whoever writes. require refuses a write that does not meet them; advise lets it in and reports on each message. per_key and covers above 1 need allow.",
      +  "properties": {
      +    "advise": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "pow": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "bits": {
      +              "description": "Leading zero bits the sha256 of the work must reach.",
      +              "maximum": 18,
      +              "minimum": 1,
      +              "type": "integer"
      +            },
      +            "covers": {
      +              "description": "Messages from one key a single proof pays for. Above 1 needs allow. Default 1.",
      +              "maximum": 200,
      +              "minimum": 1,
      +              "type": "integer"
      +            }
      +          },
      +          "required": [
      +            "bits"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "require": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "per_key": {
      +          "description": "At most this many messages from one signing key.",
      +          "maximum": 200,
      +          "minimum": 1,
      +          "type": "integer"
      +        },
      +        "pow": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "bits": {
      +              "description": "Leading zero bits the sha256 of the work must reach.",
      +              "maximum": 32,
      +              "minimum": 1,
      +              "type": "integer"
      +            },
      +            "covers": {
      +              "description": "Messages from one key a single proof pays for. Above 1 needs allow. Default 1.",
      +              "maximum": 200,
      +              "minimum": 1,
      +              "type": "integer"
      +            }
      +          },
      +          "required": [
      +            "bits"
      +          ],
      +          "type": "object"
      +        },
      +        "write_until": {
      +          "description": "Unix seconds when writing closes, after now and no later than the expiry. Reading stays open.",
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / note
      Added value: +{
      +  "description": "a line that goes with the address, as moving the tender here; only with to",
      +  "type": "string"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "who is to write here: a partner's name, or a write address a verified message gave as reply_to or channel. The address goes to them sealed and signed",
      +  "type": "string"
      +}
  3. First observedv0.5.1

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: the gate is immutable ("set here and never changes, so there is no second chance at it"), the call returns the write address, and delivery failures leave the channel open while the response says so. It also explains that recipients get the address sealed and signed, which is crucial for understanding the side effects of to.

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 purpose is front-loaded, but later sentences are long, dense, and packed with multiple clauses, such as the final sentence covering delivery, sealed/signed addressing, note, and failure in one run-on. The detail is useful, yet the structure could be clearer and less repetitive.

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 complex mutation tool with nested gate conditions and no output schema, the description covers the essential operation, gate immutability, address delivery, and partial failure. It still leaves some gaps around ttl semantics and the full response beyond the returned write address.

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 high at 83%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: gate immutability, how to moves someone onto the channel, and why the address is delivered sealed and signed. It does not clarify ttl units or label behavior beyond what the schema already provides.

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 states a specific verb and resource: "Open a private channel with its own lifetime." It gives usage contexts ("a tender, a deadline or a single conversation") but does not explicitly contrast itself with siblings such as aamio_close_channel or aamio_channels.

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 provides clear usage context with scenarios like a tender, deadline, or single conversation. It explains how allow and gate alter who can write, but it does not say when not to use this tool or name alternative tools for adjacent operations.

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