Redacted Context MCP

Overview Schema Source Related Servers Discussions Admin

Stat

redctx_stat

Read-onlyIdempotent

Returns metadata for a file or directory—redacted path, type, size in bytes, and line count—so agents can gauge size before reading lines or fetch an opaque id.

Instructions

Return metadata for one file or directory as key: value lines: id (@p_<id>), path (redacted), type (file or directory), size_bytes, and lines for text files. Use it to check a file's size or line count before choosing a redctx_read line range, or to get the opaque id of a known path; use redctx_list for many entries at once. Excluded and protected paths are refused.

Input Schema

Name	Required	Description	Default
`path`	Yes	File or directory: an `@p_<id>` reference or a root-relative path.

Output Schema

Name	Required	Description	Default
`text`	Yes	The tool output, identical to the text content block and already redacted: sensitive values appear as deterministic `[CATEGORY_<hex>]` placeholders (forms declared as aliases of one entity share its hex and add a form suffix, `[CATEGORY_<hex>.<form>]`) and files as `@p_<id>` references. When the result has `isError: true`, this is a fixed error message instead, such as a limit error or the notice that context access is blocked until the operator repairs the local redaction config.
`receipt`	Yes	Redaction statistics for this call only; never contains original values.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.10.0Oct 15, 2026

addedInput schema / properties / path / description

Added value: +"File or directory: an `@p_<id>` reference or a root-relative path."

addedOutput schema / description

Added value: +"Structured copy of every tool result: the output text plus a receipt of what redaction did."

addedOutput schema / properties / receipt / description

Added value: +"Redaction statistics for this call only; never contains original values."

addedOutput schema / properties / receipt / properties / counts_by_category / description

Added value: +"Placeholders substituted while producing this result (content and paths), keyed by category such as `PERSON`, `EMAIL` or `SECRET`; categories with none are omitted."

addedOutput schema / properties / receipt / properties / detector_profile / description

Added value: +"Active built-in detector profile: `default`, or `extended`, which adds more identifier types and prompt-injection markers."

addedOutput schema / properties / receipt / properties / detectors

Added value: +{
+  "description": "Present only when the server runs additional local detectors: one entry per detector, in load order.",
+  "items": {
+    "properties": {
+      "name": {
+        "description": "Detector name.",
+        "type": "string"
+      },
+      "nominated": {
+        "description": "Distinct values this detector nominated during the call; every occurrence of each is redacted.",
+        "type": "integer"
+      },
+      "positional": {
+        "description": "Nominated spans redacted only at their own position, because they were too long or exceeded the per-text value budget.",
+        "type": "integer"
+      },
+      "version": {
+        "description": "Detector version string.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "version",
+      "nominated",
+      "positional"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / text / description

Added value: +"The tool output, identical to the text content block and already redacted: sensitive values appear as deterministic `[CATEGORY_<hex>]` placeholders (forms declared as aliases of one entity share its hex and add a form suffix, `[CATEGORY_<hex>.<form>]`) and files as `@p_<id>` references. When the result has `isError: true`, this is a fixed error message instead, such as a limit error or the notice that context access is blocked until the operator repairs the local redaction config."

First observedv0.4.0Jun 25, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds the useful behavioral detail that excluded and protected paths are refused, which is not in annotations. It doesn't need to describe return format since an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single dense sentence front-loads the main purpose and output fields, followed by usage guidance and a refusal note. No waste, though it packs several clauses into one long sentence.

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?

Covers purpose, output fields, usage guidance, sibling routing, and refusal behavior. With annotations and an output schema present, nothing material is missing for an agent to invoke it correctly.

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% and the schema documents that path accepts an @p_<id> reference or root-relative path. The description reinforces this with `@p_<id>` and adds the context that the id is used to identify a path, but adds no syntax beyond the schema.

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?

States a specific verb (Return metadata) and resource (one file or directory), enumerates the exact output fields, and distinguishes from siblings redctx_list and redctx_read by naming them with their intended use.

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

Usage Guidelines5/5

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

Provides explicit when-to-use scenarios: check size or line count before choosing a redctx_read line range, or get the opaque id of a known path. Names redctx_list as the alternative for many entries at once.

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

Deploy Server