Skip to main content
Glama

ExitProof

by com.davisvillelabs
OverviewDiscussionsAdmin

Get Exit Manifest

get_exit_manifest
Read-onlyIdempotent

Retrieve one previously created Exit Manifest using both its manifest_id and secret access_token, without charging or changing stored state. Use when you need the preserved evidence and terms; use build_exit_pack instead when you need an actionable cancellation/refund plan, and create_exit_manifest when no manifest exists. This read is free, non-destructive, and repeatable; it does not refresh, re-evaluate, or extend the stored evidence. Missing, expired, or mismatched credentials fail without modifying the manifest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
manifest_idYesUnguessable Exit Manifest identifier returned by create_exit_manifest. It starts with xm_ followed by 32 lowercase hexadecimal characters.
access_tokenYesSecret bearer token returned by create_exit_manifest or deterministic settlement recovery. Required with manifest_id; treat it like a credential and do not log or expose it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
manifestYesStored Exit Manifest. This read does not refresh or reinterpret the original evidence.
schemaVersionYesManifest-read response schema version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / description
      Added value: +"Credentials for one previously created Exit Manifest. Both values are required together and are returned by create_exit_manifest or settlement recovery."
    • addedInput schema / properties / access_token / description
      Added value: +"Secret bearer token returned by create_exit_manifest or deterministic settlement recovery. Required with manifest_id; treat it like a credential and do not log or expose it."
    • addedInput schema / properties / manifest_id / description
      Added value: +"Unguessable Exit Manifest identifier returned by create_exit_manifest. It starts with xm_ followed by 32 lowercase hexadecimal characters."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "description": "Authenticated read of one previously stored Exit Manifest.",
+  "properties": {
+    "manifest": {
+      "additionalProperties": true,
+      "description": "Stored Exit Manifest. This read does not refresh or reinterpret the original evidence.",
+      "type": "object"
+    },
+    "schemaVersion": {
+      "const": "exitproof-manifest-read.v1",
+      "description": "Manifest-read response schema version."
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "manifest"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / access_token / pattern
      Added value: +"^xp_[A-Za-z0-9_-]{20,}$"
    • addedInput schema / properties / manifest_id / pattern
      Added value: +"^xm_[a-f0-9]{32}$"
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Although annotations already declare readOnlyHint and idempotentHint, the description adds meaningful behavioral detail: the read is free, non-destructive, repeatable, does not refresh/re-evaluate/extend evidence, and fails without modifying the manifest on missing, expired, or mismatched credentials. This goes well beyond the annotations and does not 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?

Three sentences carry the core purpose, usage conditions, sibling alternatives, and behavioral guarantees with no wasted words. The most identifying information is front-loaded, and each clause earns its place.

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

Completeness5/5

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

Given the complete input schema, an output schema, and annotations covering safety/idempotence, the description fills all remaining gaps: when to use it, what it does not do, and how failures behave. Nothing essential is missing for an agent to invoke it correctly.

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 input schema already provides 100% coverage with detailed descriptions for both manifest_id and access_token, including patterns and security guidance. The tool description adds only the general statement that both credentials are required together, which is largely restating the schema's required fields, so it stays at the baseline for high-coverage schemas.

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 opens with a specific verb and resource: 'Retrieve one previously created Exit Manifest', and immediately scopes it by the required credential pair. It also distinguishes itself from its siblings by explicitly naming when to use build_exit_pack and create_exit_manifest instead.

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

Usage Guidelines5/5

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

The description gives explicit usage guidance: use this tool when you need preserved evidence and terms, choose build_exit_pack for an actionable cancellation/refund plan, and choose create_exit_manifest when no manifest exists. This leaves little ambiguity about when to select this tool over its siblings.

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

All ExitProof 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