Skip to main content
Glama

Check a prompt for guardrails

check_guardrails
Read-onlyIdempotent

A simple pattern check, not a security review. Flags send, post, pay, delete or book words with no approval step, card-number-like digits, and mentions of passwords or API keys. Runs on the text only; nothing is sent or saved.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe prompt or instructions to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuine value by clarifying it is text-only and nothing is sent or saved, but it omits what a hit looks like and whether a clean result is distinguishable from a partial one.

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, with the most important caveat (not a security review) front-loaded and the detection list and side-effect guarantee each following in one clause. No filler.

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, read-only checker the definition covers purpose, detection scope, and side effects adequately. The only real gap is the shape of the result, which matters somewhat since no output schema exists to describe it.

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?

With a single required parameter at 100% schema description coverage, the schema already explains that `text` is the prompt to check. The description constrains the domain further (prompts/instructions, pattern-matched) but adds no format, length, or content guidance 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 names a concrete action (a pattern check over prompt text) and enumerates the exact patterns flagged: approval-less action verbs, card-number-like digits, and secret mentions. It also scopes itself negatively ("not a security review"), which helps separate it from a heavier safety tool, though no sibling is named explicitly.

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?

"A simple pattern check, not a security review" implies a lightweight pre-flight use case, but the description never states when to reach for this versus another tool, nor any precondition for running it. Usage is inferable rather than directed.

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