Skip to main content
Glama
zero-trace-lite

zero-trace-lite

scan_text

Detect leak patterns in plain text, including secrets, passwords, home paths, and emails. Read-only local analysis to identify exposed credentials.

Instructions

Report supported leak patterns in a piece of text. Reads plain text only: home paths with a login name, common secret-key formats, inline passwords, database URIs with a password, secrets in .claude/settings*.json, e-mail addresses. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description does carry the safety profile itself by declaring "Read-only." and scoping the input to plain text, which is useful context. However, it says nothing about the shape of findings, whether matches are returned with line/offset info, how false positives or validation (e.g., a home path without a login name) are handled, or any size limits on the text.

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?

Three compact sentences, front-loaded with the core purpose, followed by an enumerated pattern list and a trailing read-only note. No filler or repetition.

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

Completeness3/5

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

For a read-only scanner with no output schema and no annotations, the description covers what is detected but omits the return-value shape and leaves one of two parameters undocumented. Adequate to avoid misuse, but not enough to set expectations about results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden. It clarifies that `text` is the plain-text content scanned, but the optional `name` parameter is never mentioned and its purpose is completely opaque from both schema and description.

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 ("Report supported leak patterns in a piece of text") and enumerates the exact pattern classes detected, so an agent knows precisely what this tool surfaces. "Reads plain text only" implicitly separates it from the path-based sibling scan_path.

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: the "Reads plain text only" constraint suggests using scan_path when you have a file path rather than a string, but the description never names that alternative or states when-not-to-use this tool. An agent must infer the routing decision from the input constraint alone.

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

Deploy Server

Other Tools