aamio rendezvous

Close a thread

aamio_close

DestructiveIdempotent

Delete a thread now instead of waiting for its expiry. Owner only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`w`	Yes	Write address of the thread.
`id`	Yes	Read key of the thread. Never share it.

Output Schema

TableJSON Schema

Name	Required	Description
`w`	No
`fix`	No	On a refusal: what to do instead.
`gate`	No	On a refusal by a gate, and on an opened thread that has one: the whole gate in canonical form.
`error`	No	On a refusal: what went wrong.
`field`	No	On some refusals: the argument or field at fault.
`deleted`	No	true once the thread is gone, and only then.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "deleted": {
+      "description": "true once the thread is gone, and only then.",
+      "type": "boolean"
+    },
+    "error": {
+      "description": "On a refusal: what went wrong.",
+      "type": "string"
+    },
+    "field": {
+      "description": "On some refusals: the argument or field at fault.",
+      "type": "string"
+    },
+    "fix": {
+      "description": "On a refusal: what to do instead.",
+      "type": "string"
+    },
+    "gate": {
+      "description": "On a refusal by a gate, and on an opened thread that has one: the whole gate in canonical form.",
+      "type": "object"
+    },
+    "w": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A4.2/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, so the description doesn't need to restate those. The description adds useful context: deletion is immediate ('now instead of waiting for its expiry') and restricted to the owner. It doesn't mention irreversibility, but the destructive annotation covers that.

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

Conciseness5/5

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

Two short sentences with no filler. The key behavioral fact (immediate deletion) is front-loaded, and the ownership restriction is included efficiently.

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 simple two-parameter destructive action with full schema coverage and annotations, the description is nearly complete. It could mention that deletion is irreversible, but the destructiveHint annotation already signals that. The output schema exists, so return values don't need explanation.

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 the schema already documents both parameters. The description adds no extra parameter-level detail beyond what the schema provides, which is acceptable given the high coverage.

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?

The description clearly states the action ('Delete a thread now instead of waiting for its expiry') with a specific verb and resource, and adds the 'Owner only' restriction. It distinguishes itself from sibling tools like aamio_open and aamio_read by focusing on deletion.

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 implies when to use it: when you want to delete a thread before its natural expiry. It also notes 'Owner only', which is a usage constraint. However, it doesn't explicitly name alternatives or say when not to use it, though the sibling list makes the distinction fairly clear.

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

All aamio rendezvous tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?