Evidenceline

Show redactions

show_redactions

Read-onlyIdempotent

Show which placeholders replaced identifiers in this session, with counts per placeholder and type, plus built-in patterns, without revealing raw values.

Instructions

Show what the redaction guard rail has replaced in this session: placeholder names and counts only.

Lists each placeholder in use (for example [CLIENT-1], [ADDRESS-1], [LOT-1], [EMAIL-1], [PHONE-1]) with how many times it replaced an identifier, the totals per type, how many identities the local identifier file defines per type (none when no identifier file is loaded, in which case names are not redacted), and the built-in patterns. It never shows the raw values: they stay in the memory of the machine running this server. Use the placeholders as they are in any text you write; the person's local export puts the real values back.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`audit_log`	Yes
`explanation`	Yes
`placeholders`	Yes
`identifier_file`	Yes
`built_in_patterns`	Yes
`replacements_by_type`	Yes
`identities_configured`	Yes	Identities in the identifier file, per type.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavior beyond that: it never shows raw values, states values stay in server memory, and explains the conditional behavior when no identifier file is loaded. This is meaningful, non-redundant transparency.

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?

The first sentence front-loads the core purpose and limitation, followed by a compact, ordered explanation of output content and one usage tip. It is longer than minimal but every sentence contributes necessary detail about placeholders, counts, identities, patterns, and privacy.

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 parameterless tool with safe/idempotent annotations and an output schema, the description fully explains what is returned, what is not returned, and conditional behavior. An agent has everything needed to call and interpret the tool 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?

The tool has zero parameters, so the description needs to explain none. Baseline 4 applies because there is no parameter surface to document; the description correctly omits parameter details.

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?

Description states a specific verb ('Show') and resource ('what the redaction guard rail has replaced in this session'), and explicitly limits output to placeholder names and counts only. Includes concrete placeholder examples and distinguishes itself from browsing/searching sibling tools by focusing on redaction state.

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?

The description implies when to use the tool (when placeholders are needed for writing text) through 'Use the placeholders as they are in any text you write,' but it does not explicitly state when to use this tool versus sibling tools or when not to use it. Usage guidance is implied, not explicit.

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

Deploy Server