Skip to main content
Glama
Sign In
Clotr Guard

Clotr Guard

Official
by clotr-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Clean text

clean_text
Read-onlyIdempotent

Masks credentials and optionally personal details in text locally by replacing each finding with a placeholder and returning its kind and masked form.

Instructions

Runs check_text's check and returns the text with each finding replaced by a placeholder, plus their kinds and masked forms.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text to clean, up to 64 KiB.
include_personal_detailsNoAlso check personal details like emails. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds meaningful return-value context absent from structured fields (findings replaced by placeholder, plus their kinds and masked forms), though it doesn't specify the placeholder format or how masked forms are rendered.

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 tight sentence that front-loads the mechanism (reuses check_text's check) and then the output shape. No filler, nothing redundant.

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

Completeness4/5

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

For a simple two-parameter read-only transform with full schema coverage and no output schema, the description adequately conveys the return shape. The only remaining gap is the exact placeholder/masked-form representation, which is minor.

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 100%, including the 64 KiB limit and the include_personal_details default, so the schema carries parameter semantics. The description adds nothing about parameters, which is acceptable given full coverage but warrants only the baseline.

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+resource ('Runs check_text's check and returns the text with each finding replaced by a placeholder') and implicitly distinguishes itself from the sibling check_text by emphasizing replacement rather than plain reporting. An agent can tell what it produces without opening the schema.

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: because it 'runs check_text's check' and masks findings, an agent can infer it is the redaction counterpart to check_text, but the description never says when to choose this over check_text or when masking is inappropriate. No explicit alternatives or exclusions are given.

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

This server cannot be deployed

Other Tools