Skip to main content
Glama

membridge_redact

Read-onlyIdempotent

Mask API keys, tokens, and emails in any text to prevent leaking sensitive credentials when sharing or transferring AI memory packs.

Instructions

Mask API keys, tokens, and emails in any text.

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": {
      "text": "<text>"
    },
    "name": "membridge_redact"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds which pattern classes are targeted, which is useful, but omits whether masking is reversible, what the placeholder output looks like, and whether detection is pattern-based and may miss secrets — material gaps given there is no output schema.

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?

A single front-loaded sentence with the action first and the target categories immediately after. No filler, no redundancy, nothing to trim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, annotation-rich utility the definition is serviceable, but with no output schema the description should say what the masked text looks like and whether coverage is exhaustive. As written, an agent cannot predict the return shape or trust that all secret types are caught.

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 description coverage is 0%, but there is only one parameter, "text", whose name and type are self-explanatory and whose meaning is reinforced by "in any text." No size limits, encoding expectations, or whether the input may contain structured data are stated, so it adds little beyond the obvious.

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?

"Mask API keys, tokens, and emails in any text" gives a specific verb (mask) plus the concrete resource categories it targets, so an agent knows exactly what comes out. It does not explicitly contrast with siblings like membridge_extract or membridge_format, but the redaction framing is distinct enough to disambiguate in practice.

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 only implied: an agent can infer this is for sanitizing sensitive content before storage or sharing, but the description never states when to choose it over membridge_format or membridge_extract, nor any exclusions. No prerequisites or limits are mentioned.

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