Skip to main content
Glama

Tinplate Edge AI Safety, Security & EU Compliance

tinplate_secret_scanner_restore

Read-onlyIdempotent

Log Redact & Secret Scanner API (restore): Detect and mask leaked API keys, JWTs, and private keys in logs, diffs, and prompts. (Endpoint: POST /v1/secret-scanner/restore)

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": {
      "redacted_text": "<redacted_text>",
      "tokens": "<tokens>"
    },
    "name": "tinplate_secret_scanner_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokensYesCaller-provided map of `[SECRET_*]` placeholder tokens (max 500 entries) to original secret values.
redacted_textYesRedacted text containing `[SECRET_*]` placeholder tokens to restore.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / redacted_text / description
      Added value: +"Redacted text containing `[SECRET_*]` placeholder tokens to restore."
    • addedInput schema / properties / tokens / description
      Added value: +"Caller-provided map of `[SECRET_*]` placeholder tokens (max 500 entries) to original secret values."
  2. Changed7 schema fields changed
    • removedInput schema / properties / redacted_text / description
      Removed value: -"Parameter 'redacted_text' (e.g. \"Token: [SECRET_OPENAI_API_KEY_1]\")"
    • addedInput schema / properties / redacted_text / example
      Added value: +"export GITHUB_TOKEN=[SECRET_GITHUB_TOKEN_1]"
    • addedInput schema / properties / redacted_text / maxLength
      Added value: +262144
    • addedInput schema / properties / redacted_text / minLength
      Added value: +1
    • addedInput schema / properties / tokens / additionalProperties
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / tokens / description
      Removed value: -"Structured object parameter 'tokens'"
    • addedInput schema / properties / tokens / example
      Added value: +{
      +  "[SECRET_GITHUB_TOKEN_1]": "ghp_1234567890abcdefghijklmnopqrstuvwxyz"
      +}
  3. Added

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description does not contradict them (a pure text transform is consistent with a read-only, idempotent profile). However, the description adds almost no behavior beyond those annotations — it says nothing about what happens with unmatched placeholders, the 500-entry token cap, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a compact two-sentence form with the endpoint appended and no padding, so length is fine. The problem is prioritization: the one sentence of prose is spent on an inverted, boilerplate description instead of the restore semantics that matter.

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

Completeness2/5

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

For a simple two-parameter transform with no output schema, the description is the only place direction and preconditions can be explained, and it fails to establish that this call re-inserts secrets into previously redacted text. The schema implies the behavior, but an agent reading only the description could believe it performs scanning/masking.

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 both parameters are fully documented inline (token map semantics, max entries, placeholder format, maxLength 262144), so the schema carries the load. The description contributes no additional meaning about how redacted_text and tokens interact, which is the baseline 3 for a fully documented schema.

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

Purpose2/5

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

The name, title suffix '(restore)', and endpoint 'POST /v1/secret-scanner/restore' signal a restore operation, but the operative sentence says the tool will 'Detect and mask leaked API keys, JWTs, and private keys' — the inverse of what the schema (redacted_text + token map -> original secrets) actually does. The description never states that it un-masks/reverses a prior redaction, leaving the purpose ambiguous and partly misleading.

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

Usage Guidelines2/5

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

No when-to-use guidance is given, and the obvious counterpart 'tinplate_secret_scanner' is never named as the tool that performs the redaction this call reverses. Nothing states the precondition that the caller must already hold the placeholder-to-secret map, which is the deciding factor for whether this tool can be used at all.

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