Redacted Context MCP

Overview Schema Source Related Servers Discussions Admin

Github Repos

redctx_github_repos

Read-onlyIdempotent

List configured GitHub repo aliases from local policy to find valid repo_alias values for issue tools. Reads local configuration only and never contacts GitHub.

Instructions

List the GitHub repo aliases configured in the local policy, one per line, or OK when none are configured. Call it to find valid repo_alias values for redctx_github_list_issues, redctx_github_search_issues and redctx_github_read_issue; aliases are neutral names and the real owner/repo is never shown. It reads local configuration only and makes no GitHub request.

Input Schema

Name	Required	Description	Default
No arguments

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.

Changed6 schema fields changedv0.10.0Oct 15, 2026

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.8/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world, but the description adds non-obvious behavior: it reads local configuration only, issues no GitHub request, aliases are deliberately neutral, and the real owner/repo is never disclosed. It also defines the empty state ("OK" when none configured), which an agent could otherwise misread as an error.

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?

Two sentences, front-loaded with the primary output and its empty-state value, with usage routing second. Slight redundancy: "makes no GitHub request" largely restates openWorldHint=false, and the one-per-line output format is already implied by the output schema.

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 zero-parameter lookup with a full output schema and covering annotations, the description supplies everything needed: what it returns, the empty case, its role as the alias-discovery step, and the privacy/no-network caveat. Nothing material is missing.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing parameter-level to disambiguate. The description's only relevant note is that output lines are `repo_alias` values, which is not a parameter concern.

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 and resource ("List the GitHub repo aliases configured in the local policy") and immediately scopes it to local policy rather than remote GitHub state. It also names the three sibling tools that consume its output, so an agent can place it precisely in the toolset.

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?

Explicitly says "Call it to find valid `repo_alias` values for redctx_github_list_issues, redctx_github_search_issues and redctx_github_read_issue" — this is a clear when-to-use plus the dependency direction relative to those siblings. No inference required.

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

Deploy Server