Skip to main content
Glama

membridge_format

Read-onlyIdempotent

Converts memory exports or raw text into a ready-to-paste pack for a target AI, with API keys, tokens, and emails redacted by default.

Instructions

Convert memories into a ready-to-paste pack for a destination AI. Secrets (API keys, emails) are redacted by default.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "membridge_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPath to an export file (alternative to text).
textNoRaw memory text or JSON export content.
redactNoMask secrets (default true).
targetYesDestination format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value by disclosing that secrets are redacted by default and that the output is a paste-ready pack, which the annotations do not convey.

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?

Two short sentences, zero waste, with the core action front-loaded and the safety-relevant redaction default immediately after.

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 4-parameter, no-output-schema tool with full annotation coverage, the description covers purpose and the key default behavior. It could say more about path-vs-text precedence or output size, but nothing essential to invoking it is missing.

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 the schema already documents path, text, redact, and the target enum. The description only reinforces the redact default ('redacted by default'), adding little beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Convert memories into a ready-to-paste pack for a destination AI.' That is concrete enough to distinguish it from recall/remember/extract siblings, though it never names an alternative explicitly.

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?

Usage is implied by 'for a destination AI' — you use this when exporting memories to another model — but there is no explicit when-to-use/when-not guidance and no mention of how it relates to membridge_redact or membridge_extract.

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