Skip to main content
Glama

membridge_extract

Read-onlyIdempotent

Extract and categorize portable memories—identity, projects, stack, preferences, and rules—from raw text, ChatGPT/Claude exports, or .brain.json files to transfer AI context between tools.

Instructions

Extract and categorize portable memories (identity, projects, stack, preferences, rules) from raw text, a ChatGPT/Claude conversations.json export, or a .brain.json. Provide either "text" or "path".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "membridge_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoAbsolute or relative path to an export file.
textNoRaw memory text or JSON export content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already disclose read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context about source types and categorization categories, but does not explain what the returned memory structure looks like or how extraction handles duplicates or malformed input.

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 definition is two tight sentences with the action and categorization front-loaded, followed by the input-selection rule. There is no redundant wording.

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 two-parameter extraction tool with full schema coverage and no output schema, the description gives enough source and category context to call it correctly. A little more detail on the output or .brain.json handling would make it fully complete.

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%, so the baseline is 3. The description adds meaningful semantics by saying to provide either "text" or "path", clarifying the intended one-of usage even though the schema marks neither parameter as required.

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 uses a specific verb and resource: extract and categorize portable memories, with named categories (identity, projects, stack, preferences, rules) and accepted source types. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as membridge_remember or membridge_recall.

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?

It states the accepted inputs and that either "text" or "path" should be provided, which implies when the tool is applicable. However, it gives no explicit when-not guidance or comparison to sibling tools for storing or recalling memories.

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