Skip to main content
Glama

UAI x402 Security Tools

secret-scan

Secret scan for exposed API keys, tokens, passwords, and credentials in text — returns redacted output without exposing matched secret values. Ideal for agent pre-flight checks before sharing config or logs. (REST equivalent: POST /api/v1/secret-scan, $0.01)

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": "secret-scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to scan for exposed secrets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations carry only a title, so the description does most of the work, and it delivers the key behavioral fact: output is redacted and never exposes matched secret values. It also reveals the REST equivalent endpoint and a $0.01 cost, useful for budgeting and parity. It stops short of stating whether input text is stored/logged or what detections are produced, which matters for a scanner handling sensitive input.

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 short sentences, front-loaded with what the tool does, followed by the safety-relevant output guarantee, then a use case and the REST/pricing note. Nothing is redundant and no sentence can be removed without losing information.

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

Completeness4/5

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

For a one-parameter tool with no output schema, the description covers purpose, input domain, and the salient output property (redacted, secrets not echoed). The remaining ambiguity is whether the return is redacted text or a findings list, which an agent would need to know to consume the result.

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?

The tool takes a single parameter whose schema description ('Text to scan for exposed secrets') is fully covered, so the schema already carries the semantics and the baseline of 3 applies. The description reinforces it by saying the scan operates on 'text' and mentioning config or logs as typical payloads, adding a small amount of meaning beyond the schema.

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 specific verb and resource ('Secret scan for exposed API keys, tokens, passwords, and credentials in text') that an agent can match against a task immediately. It distinguishes itself from most siblings by scope (text input, credential detection), though it never names the closely related 'secret-scan-preview' sibling to clarify the difference.

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?

It supplies a concrete usage context — 'Ideal for agent pre-flight checks before sharing config or logs' — which is genuine when-to-use guidance. However, there is no when-not guidance and no routing to alternatives such as the preview variant or the GitHub Actions secret exposure sibling, leaving the agent to infer which secret tool to pick.

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