Skip to main content
Glama

ExitProof

by com.davisvillelabs
OverviewDiscussionsAdmin

Get Exit Manifest

get_exit_manifest
Read-onlyIdempotent

Retrieve one previously created Exit Manifest without charging or changing stored state. Pass manifest_id and access_token together: the ID selects the record and the secret token authorizes access to that same record, so neither value is sufficient alone. Use this for preserved evidence and terms; use build_exit_pack for an actionable cancellation/refund plan, or create_exit_manifest when no manifest exists. This free, repeatable read does not refresh, re-evaluate, or extend 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.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces and extends this with valuable specifics: the operation is free, repeatable, does not refresh/re-evaluate/extend evidence, and missing/expired/mismatched credentials fail without modifying the manifest. This adds meaningful behavioral context beyond the annotations.

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 dense but not bloated; each sentence earns its place. It front-loads the core purpose and read-only guarantee, then handles credential pairing, usage guidance, and behavioral caveats without redundant phrasing.

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 output schema, annotations, and sibling list, the description covers everything needed to call the tool correctly: what it returns conceptually, how the two parameters interact, when to choose alternatives, and what side effects do not occur. No critical operational gap remains.

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 100% with detailed patterns and descriptions for both parameters. The description adds cross-parameter semantics by stating that manifest_id and access_token must be passed together and that neither value is sufficient alone, plus a security caution to treat the token as a credential. This is useful context beyond the schema, though it does not need to repeat field-level details.

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.' It immediately clarifies the read-only nature ('without charging or changing stored state') and names the sibling alternatives it is not, so an agent can distinguish it from build_exit_pack and create_exit_manifest without opening schemas.

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 explicitly states when to use this tool ('Use this for preserved evidence and terms') and gives concrete alternative conditions: build_exit_pack for an actionable cancellation/refund plan and create_exit_manifest when no manifest exists. This is strong routing guidance that goes beyond the sibling list.

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