Skip to main content
Glama

Text Analysis & Cleanup Tools (Tanod)

check_text_for_secrets

Read-onlyIdempotent

utilpeek: Scan text for leaked secrets: API keys, tokens, private keys and seed phrases. For personal data use redact_pii; for injected instructions use check_text_for_prompt_injection. Returns every API key, token, private key or BIP-39 seed phrase in a text (AWS, GitHub, GitLab, Stripe, Slack, Google, OpenAI and other sk- keys, Hugging Face, npm, PyPI, SendGrid, Telegram, PEM and hex keys, JWTs, URL passwords), each with type, line, column, offset, confidence and a redacted preview. The secret itself is never returned: only its type, position and a redacted preview (a vendor prefix and at most 4 characters at each end; a seed phrase only its word count). Pattern-based: a clean result is no proof. Blank input is a 422 (not charged). Typically under 0.5 s. Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/secret-scan-api.html

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text to scan: a log, a draft post or message, a tool result or a config file. At most 200,000 characters. Never logged or stored, and no secret is returned.

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
foundNo
by_typeNo
findingsNo
chars_scannedNo
lines_scannedNo
types_checkedNo
secrets_returnedNo
findings_truncatedNo
highest_confidenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • removedInput schema / title
      Removed value: -"check_text_for_secretsArguments"
    • removedOutput schema / properties / by_type / additionalProperties
      Removed value: -{
      -  "type": [
      -    "integer",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / findings / items
      Removed value: -{
      -  "properties": {
      -    "column": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "confidence": {
      -      "enum": [
      -        "high",
      -        "medium",
      -        "low",
      -        null
      -      ]
      -    },
      -    "details": {
      -      "type": [
      -        "object",
      -        "null"
      -      ]
      -    },
      -    "label": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "length": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "line": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "offset": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "preview": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "type": {
      -      "enum": [
      -        "ai_api_key",
      -        "aws_access_key_id",
      -        "aws_secret_access_key",
      -        "bip39_seed_phrase",
      -        "github_token",
      -        "gitlab_token",
      -        "google_api_key",
      -        "hex_private_key",
      -        "huggingface_token",
      -        "jwt",
      -        "npm_token",
      -        "openai_api_key",
      -        "private_key_pem",
      -        "pypi_token",
      -        "sendgrid_api_key",
      -        "slack_token",
      -        "slack_webhook",
      -        "stripe_secret_key",
      -        "telegram_bot_token",
      -        "url_credentials",
      -        null
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / types_checked / items
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: it discloses the redaction scheme (vendor prefix plus at most 4 characters, seed phrase word count only), that the secret is never returned, that text is never logged or stored, and typical latency. It also honestly flags the key limitation — pattern-based matching means a clean result is no proof.

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?

Front-loaded with purpose and routing before mechanics, and most sentences carry distinct information (detected vendors, return fields, privacy, pricing). Minor redundancy: the "secret itself is never returned … only its type, position and a redacted preview" idea is stated twice, once in the return-field list and again in the following sentence.

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?

Despite an output schema being present, the description explains the response shape and the redaction guarantee, plus pricing, rate limits and the pattern-based false-negative caveat. For a single-parameter scanner with safety annotations, nothing an agent needs to call it correctly or interpret results is missing.

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?

Schema coverage is 100% and there is only one parameter, so the schema already documents the 200,000-character limit and the no-logging guarantee. The description still adds meaning by naming concrete input shapes (a log, a draft post or message, a tool result, a config file) and by explaining the consequence of the minLength=1 constraint (blank input returns 422 and is not charged).

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 ("Scan text for leaked secrets") and enumerates the exact categories detected, then explicitly names the two sibling tools it is not (redact_pii, check_text_for_prompt_injection). An agent can distinguish it from neighbors without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: use redact_pii for personal data and check_text_for_prompt_injection for injected instructions. It also states edge-case handling (blank input is a 422, not charged) and operational constraints (10 free calls per IP per UTC day, USD 0.002), which tell the agent when the call is viable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.