Skip to main content
Glama

Ausca

by com.ausca
OverviewDiscussionsAdmin

Admit or replay one Agent Inbox invocation

ausca_open_inbox
DestructiveIdempotent

Admit or replay one idempotent paid Agent Inbox invocation when settlement authority is supplied by the host boundary. Only envelopes for the inbox.receive offer are admitted on this resource. The result starts a renewable inbox; while it remains active, inbox.extend can add a supported increment without changing its address or contents.

Input Schema

NameRequiredDescriptionDefault
inputYes
offer_idYes
offer_revisionYes
idempotency_keyYes
input_schema_digestYes
output_schema_digestYes
offer_revision_digestYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedOutput schema / $defs / ArtifactEvidence / properties / artifact_ref
      Removed value: -{
-  "$ref": "#/$defs/ArtifactRef"
-}
    • addedOutput schema / $defs / ArtifactEvidence / properties / artifact_uri
      Added value: +{
+  "$ref": "#/$defs/ArtifactUri"
+}
    • changedOutput schema / $defs / ArtifactEvidence / required
      Previous value: -[
-  "artifact_ref",
-  "content_digest",
-  "media_type",
-  "size_bytes",
-  "created_at"
-]New value: +[
+  "artifact_uri",
+  "content_digest",
+  "media_type",
+  "size_bytes",
+  "created_at"
+]
    • removedOutput schema / $defs / ArtifactRef
      Removed value: -{
-  "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
-  "maxLength": 512,
-  "minLength": 1,
-  "type": "string"
-}
    • addedOutput schema / $defs / ArtifactUri
      Added value: +{
+  "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
+  "maxLength": 512,
+  "minLength": 1,
+  "type": "string"
+}
    • addedOutput schema / $defs / X402PaymentRequired / properties / accepts / items / title
      Added value: +"X402PaymentRequirements"
    • addedOutput schema / $defs / X402PaymentRequired / properties / resource / title
      Added value: +"X402ResourceInfo"
    • addedOutput schema / $defs / X402PaymentRequired / title
      Added value: +"X402PaymentRequired"
  2. Changed3 schema fields changed
    • removedInput schema / $defs / ParentBinding
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "execution_digest": {
-      "$ref": "#/$defs/Digest"
-    },
-    "invocation_id": {
-      "$ref": "#/$defs/Identifier"
-    }
-  },
-  "required": [
-    "invocation_id",
-    "execution_digest"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / attribution
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "campaign": {
-      "maxLength": 128,
-      "pattern": "^[a-z0-9][a-z0-9._-]{0,127}$",
-      "type": "string"
-    },
-    "source": {
-      "maxLength": 64,
-      "pattern": "^[a-z0-9][a-z0-9._-]{0,63}$",
-      "type": "string"
-    }
-  },
-  "required": [
-    "source"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / parent_binding
      Removed value: -{
-  "$ref": "#/$defs/ParentBinding"
-}
  3. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare idempotent, destructive, open-world, and non-read-only behavior. The description adds useful context beyond those hints: settlement authority is host-supplied, only inbox.receive envelopes are admitted, the result starts a renewable inbox, and inbox.extend can add an increment without changing address or contents. It does not explain the destructive implication or payment/cost mechanics in detail.

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 three sentences, front-loads the action and precondition, then adds admission scope and post-call behavior. It is dense but not padded; some jargon is unexplained, but each sentence contributes useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with 7 required parameters and no schema field descriptions, so the description should carry more parameter and invocation detail than it does. It covers purpose, precondition, offer restriction, and follow-on behavior, and an output schema exists, but the missing parameter semantics leave an agent without enough guidance to construct a valid call confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all 7 parameters are required, but the description does not explain offer_id, offer_revision, the three digest parameters, the nested input payload, or idempotency_key. The references to 'offer' and 'idempotent' are only generic hints and do not map meaning to specific fields.

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 verb pair, resource, and admission scope: 'Admit or replay one idempotent paid Agent Inbox invocation' and 'Only envelopes for the inbox.receive offer are admitted.' It distinguishes this from inbox.extend by describing the latter as a follow-on action, though it does not explicitly contrast with sibling tools like ausca_prepare_invocation.

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?

It states a clear precondition ('when settlement authority is supplied by the host boundary') and an exclusion ('Only envelopes for the inbox.receive offer'), and mentions the extend path once the inbox is active. It does not comprehensively say when to choose this over all sibling preparation or lookup tools, but the main usage context is clear.

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

All Ausca toolsInspect
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