Skip to main content
Glama
crunchtools

io.github.crunchtools/airlock

Official
by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Content Tool

content_tool

Judge inline text as untrusted to prevent prompt injection, with options to block, flag, or redact based on trentina_mode.

Instructions

Judge inline text through all three layers. It is always untrusted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe text to judge
content_typeNoIts media type; text/html is converted to Markdowntext/plain
trentina_modeNoblock, flag, or {"redact": "<what you need>"}
trentina_preprocessNofalse for exact text; see the server instructions

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.43.1
    • changedInput schema / properties / content_type / description
      Previous value: -"Its media type; text/html is converted to Markdown by default"New value: +"Its media type; text/html is converted to Markdown"
    • changedInput schema / properties / trentina_mode / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": false,
+    "description": "``trentina_mode: {\"redact\": \"<question>\"}``: extract, instead of deliver.",
+    "properties": {
+      "redact": {
+        "description": "What to extract",
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "redact"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / trentina_mode / description
      Previous value: -"block, redact or flag; see the server instructions"New value: +"block, flag, or {\"redact\": \"<what you need>\"}"
    • changedInput schema / properties / trentina_preprocess / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / trentina_preprocess / description
      Previous value: -"Pre-processors to apply; see the server instructions"New value: +"false for exact text; see the server instructions"
    • removedInput schema / properties / trentina_prompt
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "What to extract, for redact"
-}
  2. Addedv0.37.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds a meaningful security context ('always untrusted'), but says nothing about side effects, permissions, rate limits, or whether the operation is read-only or mutating.

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?

Two short sentences are front-loaded and contain no filler. The terseness contributes to the definition's clarity problems, but the text itself is appropriately sized.

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?

Although an output schema exists and parameter coverage is complete, the description is too thin for a tool with no annotations and several unusual parameters. It does not explain the three layers, intended use case, or behavioral traits, leaving significant gaps for the agent.

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 the schema already documents all four parameters. The description's phrase 'all three layers' may loosely hint at the block/flag/redact modes, but it does not add concrete parameter meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Judge inline text'), but 'through all three layers' is undefined and cryptic. It does not distinguish this tool from siblings like fetch_tool or read_tool, leaving the agent to guess what the three layers are or what judgment 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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only contextual hint is 'It is always untrusted,' which suggests a security use case but does not route the agent between this tool and its many siblings.

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