Skip to main content
Glama

Secrets scanner

secrets_detection
Read-only

Scan code for leaked secrets, API keys, tokens, and credentials. Detects 16+ secret types including AWS keys, GitHub tokens, Stripe keys, private keys, JWTs, database URLs, and high-entropy strings. Returns redacted previews with severity levels and rotation recommendations. No external API — pure regex pattern matching. Costs $0.005 USDC per call.

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": {
      "code": "<code>"
    },
    "name": "secrets_detection"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCode string to scan for secrets
filenameNoOptional filename for context (e.g. 'config.ts', '.env.example')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces that with 'no external API,' and adds substantive traits the annotations don't cover: the detection breadth (16+ types, high-entropy strings), the redacted output shape with severity levels and rotation recommendations, and the per-call price. It stops short of describing pagination, size limits on the code string, or false-positive behavior.

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?

Four tight sentences with the purpose front-loaded, then detection coverage, then output shape, then operational constraints (no external API, price). No repetition and nothing that could be cut without losing information.

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, and the description compensates by describing the return value (redacted previews, severity levels, rotation recommendations). Combined with the pricing and offline-execution note, an agent has everything needed to decide and call correctly.

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 coverage is 100%, so both parameters and their meaning are already documented in the schema. The description mentions what is detected but adds nothing about the 'code' or 'filename' parameters beyond what the schema states, so the baseline 3 applies.

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 code for leaked secrets, API keys, tokens, and credentials.' The scope is clearly code-string scanning rather than contract auditing or token risk scoring, which is enough to separate it from siblings like token_security or dependency_risk_score.

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?

Gives real decision context: 'No external API — pure regex pattern matching' and 'Costs $0.005 USDC per call,' which tells an agent this is deterministic, offline, and paid per invocation. It never names an alternative or an explicit when-not case, so it falls short of a 5.

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.

Resources