Skip to main content
Glama
Clotr Guard

Clotr Guard

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Clotr checks text on this computer and returns each finding's kind and a masked form, never the full value. Call check_text before you send text that may hold a credential to another tool or service. Call clean_text when you want a copy with the findings replaced. Call is_secret_file before you read a local file. Clotr checks only what you pass it and stops nothing itself.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_textA

Check text for credentials before it leaves this computer or goes to another tool. Returns kinds and masked forms, and blocks nothing.

clean_textA

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

is_secret_fileA

Call before reading a local file. True means Clotr treats the path as a secret file, so don't read it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 3 tools

Disambiguation4/5

check_text and clean_text operate on the same input (text) and could be confused at a glance, but the descriptions clearly differentiate detection-only from redaction-with-placeholders. is_secret_file targets a completely different resource (file paths) and is unambiguous.

Naming Consistency4/5

check_text and clean_text follow a consistent verb_noun pattern, and is_secret_file is a readable predicate form that fits its boolean-returning behavior. The minor deviation in style (is_ prefix) is natural and doesn't impede understanding.

Tool Count5/5

Three tools is a tight, well-scoped surface for a credential-guard utility: detect, redact, and path-check. Each tool clearly earns its place with no filler.

Completeness4/5

The core lifecycle — check text, clean text, and vet file paths before reading — is covered. Minor gaps exist, such as no tool for scanning file contents directly or configuring custom detection patterns, but agents can compose the existing tools to work around this.

Maintenance

ActivityActive
ResponsivenessUsually handled