Skip to main content
Glama
Sign In
shellward

shellward

by jnMetaCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_injection

Scans text for prompt injection attempts using 37+ rules for Chinese and English, including hidden character detection.

Instructions

Detect prompt injection attempts in text. Supports 37+ rules for Chinese and English, with hidden character detection.

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_injection"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to scan for injection attempts
thresholdNoDetection threshold 0-100 (default: 40, lower = stricter)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.1
    • changedInput schema / properties / threshold / description
      Previous value: -"Detection threshold 0-100 (default: 60, lower = stricter)"New value: +"Detection threshold 0-100 (default: 40, lower = stricter)"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral transparency. It discloses supported rules count (37+) and language support, but does not specify return format, side effects, or behavior when injection is detected. It adds some context but not comprehensive.

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?

Two sentences with no redundant information. The most critical capability (detect prompt injection) is front-loaded, followed by supportive details.

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?

The description lacks details about output format (e.g., boolean, score, or report) and threshold behavior beyond the schema definition. For a detection tool with no output schema, an agent would benefit from knowing what to expect upon invocation.

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?

The input schema has 100% coverage with descriptions for both parameters. The description adds no additional parameter-level detail beyond the schema, meeting the baseline expectation.

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 clearly states 'Detect prompt injection attempts in text,' using a specific verb (detect) and resource (text). It differentiates from sibling tools like check_command and check_path by specifying injection detection with support for Chinese and English and hidden character detection.

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?

The description implies usage for detecting prompt injections but does not explicitly state when to use this tool versus alternatives like check_command or scan_data. No exclusions or alternative tool mentions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools