Skip to main content
Glama
Sign In
Agent Receipts

Agent Receipts

by webaesbyamin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

memory_import_bundle

Import a memory bundle while verifying checksums and skipping duplicates. Each import is recorded as a signed receipt for cryptographic accountability.

Instructions

Import a memory bundle from another Agent Receipts instance. Verifies checksums before importing. Skips memories that already exist locally. The import operation itself is recorded as a signed receipt.

Input Schema

NameRequiredDescriptionDefault
bundleYesThe memory bundle JSON object to import
skip_existingNoSkip entities/observations that already exist (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses checksum verification, skipping existing memories, and recording the import as a signed receipt. This is good for a write operation, though it doesn't mention potential failure modes.

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 three sentences, front-loaded with purpose, and contains no fluff. Every sentence provides essential 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?

For a tool with no output schema and no annotations, the description covers purpose, input handling, deduplication, and side effects. It lacks explanation of return values, but that is partially compensated by the schema coverage.

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?

Schema coverage is 100%, so baseline is 3. The description adds context for 'bundle' (from another instance) and aligns with 'skip_existing' schema, but doesn't compensate beyond that.

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 clearly states the tool imports a memory bundle from another instance, using specific verbs ('Import') and resources ('memory bundle'). It distinguishes from siblings like 'memory_export_bundle' by focusing on import behavior.

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

Usage Guidelines3/5

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

The description mentions importing from another instance and skipping existing memories, but lacks explicit guidance on when to use this tool versus alternatives (e.g., memory_audit, memory_context). It does not state when not to use it.

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

Deploy Server

Other Tools