Skip to main content
Glama

injection_scan

Read-only

Rule-based scan of a text blob (max 50 KB) for prompt-injection patterns: instruction overrides, role hijack, hidden unicode, base64 payloads, tool/webhook exfil, markdown image exfil. Returns risk, matches with offsets, and a sanitized copy marked untrusted. Heuristic only; text is not stored. Price: 0.005 USDC per call (x402, Base).

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

Input Schema

NameRequiredDescriptionDefault
textYesText to scan (max 50 KB)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the 50 KB ceiling, that text is not stored, that results are heuristic (so false positives/negatives are possible), that a sanitized untrusted copy is returned, and the exact cost mechanism (0.005 USDC per call via x402 on Base). Those are precisely the operational facts an agent needs before committing a paid call, and none of them appear in the annotations.

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?

It is a single dense sentence but well front-loaded: capability first, then pattern list, then return values, then caveats and price. The parenthetical cost clause is somewhat tacked on, but no phrase is genuinely wasted.

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?

With no output schema, the description carries the return-value burden and does so: risk level, matches with offsets, and a sanitized marked copy. Combined with the size limit, non-storage guarantee, heuristic caveat, and pricing, nothing an agent needs to invoke this correctly is missing.

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?

There is a single required parameter whose schema description already covers its meaning and size limit at 100% coverage, so the baseline applies. The description restates the 50 KB maximum but adds no syntax, encoding, or formatting detail beyond the schema.

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?

The description names a specific verb and resource ('Rule-based scan of a text blob') and enumerates the exact pattern classes detected: instruction overrides, role hijack, hidden unicode, base64 payloads, tool/webhook exfil, markdown image exfil. It also names the outputs, so an agent can distinguish this from any sibling without opening the schema.

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 implied rather than stated: an agent can infer it is meant to check untrusted text, and the 'Heuristic only' caveat hints at the limits of the result. There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for cases this tool does not cover.

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