Skip to main content
Glama

Prompt guard

prompt_guard
Read-onlyIdempotent

Scan untrusted text for prompt injection, jailbreak attempts, delimiter spoofing, wallet exfiltration, and encoded payloads ($0.001). $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
textYesUntrusted text or prompt payload to scan (up to 32000 chars)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds real context beyond that: a fixed $0.001 cost, the x402 payment protocol, accepted assets (USDC on Arc/Base/Solana, XNT on X1), and the sign-then-resubmit flow. It does not describe the verdict/response shape an agent should expect, leaving a gap for a scanner.

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?

Purpose is front-loaded, followed by price and then payment mechanics, with no preamble. The $0.001 figure is stated twice, a minor redundancy, but overall every sentence carries operational information.

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

Completeness3/5

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

Covers purpose, cost, and payment wiring well, which is the hard part of this tool. With no output schema, the description never indicates what a scan returns (a verdict, a risk score, matched categories), so an agent cannot anticipate the result shape.

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%, so baseline is 3, but the description adds genuine meaning: it explains that `payment` is obtained by calling first without it, signing the returned terms with your own wallet, then resubmitting. That prerequisite chain is not evident from the schema alone.

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 ('Scan') on a specific resource ('untrusted text') and enumerates the exact threat classes it detects: prompt injection, jailbreak, delimiter spoofing, wallet exfiltration, encoded payloads. An agent knows precisely what this does and it is clearly distinct from the arc_* payment/market siblings.

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?

Explains the two-step invocation procedure explicitly ('Call once without payment for the terms, sign them with your own wallet, call again with payment'), which is the key usage pattern. It lacks an explicit statement of when to prefer this over a sibling or when scanning is unnecessary, 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.