Skip to main content
Glama
Sign In
Clotr Guard

Clotr Guard

Official
by clotr-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Check a file path

is_secret_file
Read-onlyIdempotent

Checks whether a local file path is treated as secret before reading it, returning true when the file should be skipped to protect credentials and personal data.

Instructions

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

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": {
      "path": "<path>"
    },
    "name": "is_secret_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe file's path, absolute or relative to where the server runs. The file isn't read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world check, so the safety profile is covered. The description adds value beyond that by explaining what the return value signifies and prescribing the follow-up action (do not read the file), which annotations cannot convey.

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?

Two short sentences with zero filler; the trigger condition comes first and the result semantics follow. Every clause earns its place.

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?

There is no output schema, so the description must carry return semantics, and it does by defining what a true result means and the action it implies. For a single-parameter predicate with fully annotated safety hints, nothing an agent needs is missing.

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% and the schema already states the path may be absolute or relative to the server's working directory and that the file is not read. The description adds no additional param syntax or constraints, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource: check whether a local file path is treated as a secret file, and it explains the boolean result's meaning. It doesn't explicitly distinguish itself from clean_text or check_text, but those operate on text content rather than file paths, so the distinction is implicit rather than stated.

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

Usage Guidelines4/5

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

"Call before reading a local file" establishes the trigger condition clearly, and the instruction not to read when the result is true gives an actionable when-not rule. No alternatives are named, but the sibling tools are unrelated to path gating, so there's little to route between.

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