Skip to main content
Glama

Caelara Labs Web Intelligence

prompt_firewall_structurer

Scan a prompt for injection/PII and return a structured form

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": {
      "prompt": "<prompt>"
    },
    "name": "prompt_firewall_structurer"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesPrompt text
strictNoStrict mode
contextNoAdditional context

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden and does very little with it. It never says whether the scan blocks, flags, or merely reports, what verdict fields the structured form contains, whether the prompt is stored or logged, or what 'strict' mode changes. The only behavioral signal is that detection covers injection and PII.

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?

A single front-loaded sentence with no filler, and the object of the scan precedes the output clause. It is efficient, though the terseness contributes to the specification gaps noted elsewhere.

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?

With no output schema and no annotations, the description is the only place a caller could learn what the 'structured form' returns or how the verdict should be interpreted, and it supplies neither. For a security-screening tool where the agent must decide what action to take on the result, that is a material omission.

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%, so all three parameters are documented in the schema itself and the baseline of 3 applies. The description adds nothing about 'strict' (the one non-obvious knob) or about how 'context' influences detection, so it neither compensates nor detracts.

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?

States a specific verb (Scan) and resource (a prompt), plus the two things it looks for (injection and PII) and the output shape (structured form). The sibling list contains no comparable scanning tool, so no differentiation is required. It stops short of 5 only because it doesn't say what 'structured form' concretely means.

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?

There is no when-to-use guidance, no stated prerequisites, and no mention of when NOT to run the scan (e.g., already-trusted input) or of any alternative tool. An agent must infer that this is the pre-flight safety check before handling untrusted prompt text.

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