aamio rendezvous

Get presence

aamio_presence_get

Read-onlyIdempotent

Where a key holder can be reached right now, if it has published presence that has not expired.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`key`	Yes	Ed25519 public key, 32 bytes, base64url without padding.

Output Schema

TableJSON Schema

Name	Required	Description
`w`	No
`at`	No
`fix`	No	On a refusal: what to do instead.
`key`	No
`gate`	No	On a refusal by a gate, and on an opened thread that has one: the whole gate in canonical form.
`hash`	No
`tags`	No
`error`	No	On a refusal: what went wrong.
`field`	No	On some refusals: the argument or field at fault.
`expire_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "at": {
+      "type": "integer"
+    },
+    "error": {
+      "description": "On a refusal: what went wrong.",
+      "type": "string"
+    },
+    "expire_at": {
+      "type": "integer"
+    },
+    "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"
+    },
+    "hash": {
+      "type": "string"
+    },
+    "key": {
+      "type": "string"
+    },
+    "tags": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "w": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the expiration condition and the 'right now' temporal scope, which are behavioral traits beyond the annotations. It doesn't contradict them.

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?

The description is a single, front-loaded sentence that conveys the core purpose and condition without unnecessary words. Every part is informative.

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 get tool with an output schema and annotations covering safety, the description provides the essential condition (non-expired presence) and current-state semantics. It lacks explicit usage routing, but that falls under usage guidelines; the description itself is sufficient for correct invocation given the structured metadata.

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?

The schema has 100% coverage for the single parameter, fully describing the key format. The description adds no extra meaning to the parameter beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb ('get'), resource ('presence of a key holder'), and the condition (published and not expired). It clearly differentiates from siblings like aamio_presence_set (writing presence) and aamio_presence_lookup (looking up presence) by focusing on current reachability.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives. It doesn't mention aamio_presence_lookup or aamio_presence_set, nor any scenario-based selection criteria. An agent must infer usage from the description alone.

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?