Skip to main content
Glama

get_agent_continuity_passport

Read-onlyIdempotent

Export a privacy-preserving agent continuity passport as JSON-LD with identity anchor, witness hashes, recovery, and layer quality metadata.

Instructions

Export a privacy-preserving Agent Continuity Passport as JSON-LD: identity anchor, witness hashes, continuity, recovery, relation, quality by layer, and PROV-O mapping. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional max sessions to scan
agent_idNoStable agent id to export
session_idNoOptional session scope; if agent_id is omitted, it is inferred from the session
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
export_formatNoOptional export format
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
include_privateNoOptional: include sanitized recent artifact previews. Requires x-delx-agent-token or agent_token. Default false for public exports.
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description doesn't need to repeat safety traits. It adds behavioral context with 'privacy-preserving' and 'Free', but doesn't elaborate on other behaviors like return format or pagination. This adds some value beyond 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 a single sentence that is highly concise yet informative. It front-loads the main action and key details, with no wasted words or redundant information.

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?

Given the tool's complexity (8 parameters, no output schema), the description adequately explains the output contents and format. It does not explain parameter relationships or provide examples, but the schema covers parameters well. The lack of output schema is somewhat mitigated by the description of the passport components.

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 has 100% description coverage for all 8 parameters, so the schema already documents parameter semantics. The description does not add any additional meaning or constraints beyond the schema. Baseline score of 3 applies.

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 uses the specific verb 'Export' and explicitly identifies the resource 'Agent Continuity Passport' as JSON-LD, listing its contents (identity anchor, witness hashes, etc.). This clearly distinguishes it from sibling tools that deal with witness lineage or graphs.

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 does not provide any guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions. The sibling list includes many related tools, but the description offers no comparative advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/delx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server