ltm
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lsB | List recent packets on the configured ltm server. Returns a table with ID, creation time, and goal. |
| showA | Fetch a packet by ID and return a human-readable summary (goal, constraints, decisions, attempts, next step). |
| pullA | Fetch a packet by ID and return the raw JSON document. Use when you need the full v0.2 packet — otherwise prefer 'show' or 'resume'. |
| resumeB | Render a prompt-ready resume block for a packet so the current agent can continue prior work. Output is markdown intended to be treated as authoritative context. |
| pushA | Send a Core Memory Packet to the configured ltm server. The packet is schema-validated and scanned for secrets/absolute paths before upload. Pass the packet as a JSON object under 'packet'. Use 'ltm example' via the 'example' tool if you need a valid shape reference. |
| saveA | Save the current session as a Core Memory Packet. Build the packet JSON from the active conversation — goal, locked decisions, failed attempts, open questions, next step — and pass it as 'packet'. Same validation and redaction as 'push'; use this when the intent is 'persist my session' rather than 'ship a pre-built packet'. |
| rmA | Delete a packet by ID from the server. Destructive — confirm with the user before calling. |
| publishA | Publish a packet to a public URL anyone can view (no account required) and copy as a prompt. The URL is unguessable (it embeds the packet's ULID). Returns the public URL. Idempotent — re-publishing a published packet preserves the original URL and timestamp. Confirm with the user before calling: this makes the packet content world-readable. |
| unpublishA | Revoke public access to a previously published packet. The packet itself is not deleted — only the public URL stops working. |
| exampleA | Return an embedded sample v0.2 Core Memory Packet. Useful as a shape reference before calling 'push'. No server round-trip. |
| whoamiA | Report the configured ltm host and a short fingerprint of the stored token. Use to verify the server the MCP will hit before pushing. |
| platformA | Return the URL of the managed ltm platform's web dashboard so the agent can surface it to the user. Errors when the user is configured against a self-hosted server. No server round-trip. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clear, distinct purpose. For example, 'push' sends pre-built packets while 'save' persists session state, and 'show' returns a summary vs 'pull' returns raw JSON. No overlap causes confusion.
All tool names are lowercase single words, but they mix short names (ls, rm) with full words (publish, resume) and a few noun forms (example, platform). While the style is uniform, the part-of-speech varies slightly.
With 12 tools, the server covers core packet management (CRUD, listing, publishing, session saving) without being bloated. Each tool earns its place for a focused domain.
The tool set lacks an update operation for packet content (only delete+re-push). Additionally, there is no filtering or search capability beyond listing all packets. These are notable gaps for a complete lifecycle.