Skip to main content
Glama
Sign In

netcafe-devkit

by com.ainetcafe
OverviewDiscussionsAdmin

Redact secrets and PII before sending text on

redact_text
Read-onlyIdempotent

Strip emails, phone numbers, ID numbers, API keys, private keys, JWTs, card numbers and IPs out of text, returning the redacted text plus a mapping table to restore them afterwards. Rule-based only — no model sees the input. The same value always maps to the same placeholder, so the answer can be restored.

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": "redact_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyNoOptional comma-separated subset, e.g. "EMAIL,API_KEY,PRIVATE_KEY".
textYesThe text to redact.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond annotations by disclosing that processing is rule-based, no model sees input, and same values map to the same placeholders for restorability. These details add meaningful behavioral context beyond the readOnlyHint and idempotentHint annotations.

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 compact sentences, front-loaded with the core action and return value, then adding a key behavioral guarantee. No filler or repetition of schema/annotations.

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

Completeness5/5

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

For a two-parameter tool with a rich output schema and strong annotations, the description fully covers the core function, privacy model, deterministic mapping, and restoration capability. It is complete for an agent to select and invoke correctly.

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?

Input schema covers both parameters with clear descriptions (text, optional 'only' subset), so baseline is 3. The description adds no extra parameter-level details, but it does list the entity types that will be redacted by default, which indirectly informs the 'only' filtering behavior.

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 uses a specific verb ('Strip') and enumerates the exact resource types (emails, phone numbers, ID numbers, API keys, etc.), making it clear what the tool does. It also explicitly differentiates from sibling tools like diff_text and json_format by focusing on redaction and returning a restoration mapping.

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

Usage Guidelines4/5

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

The phrase 'before sending text on' establishes a clear use case, and 'Rule-based only — no model sees the input' provides important context about when this is preferable. It does not explicitly name alternative tools for exclusion, but the sibling list contains no other redaction tool, so distinction is inherent.

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

All netcafe-devkit toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources