Skip to main content
Glama
crunchtools

io.github.crunchtools/airlock

Official
by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Read Tool

read_tool

Read local text files through layered prompt-injection defenses, rejecting binary input and returning sanitized Markdown.

Instructions

Read a local text file through all three layers. Binary is rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the file to read
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. Changed5 schema fields changedv0.43.1
    • 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.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that binary input is rejected, which is useful, but leaves "all three layers," permission needs, and what the trentina modes actually do entirely unexplained.

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, front-loaded sentences with no filler. It is efficient, though the extreme terseness borders on under-specification for a tool with a non-obvious three-parameter surface.

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?

For a tool with three parameters, an unexplained "three layers" concept, and no annotations, the description is too thin. The presence of an output schema removes the need to describe return values, but the redaction/preprocess semantics are still not made intelligible.

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 documents path, trentina_mode, and trentina_preprocess, and output_schema exists. The description adds no parameter meaning beyond that, making the baseline 3 appropriate here.

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 verb+resource are specific ("Read a local text file"), which distinguishes it from fetch_tool/search_tool siblings that operate on other sources. However, the phrase "through all three layers" is unexplained internal jargon that adds ambiguity rather than clarity.

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?

The only guidance given is that binary files are rejected; there is no statement of when to use this tool versus fetch_tool, content_tool, or search_tool, and no exclusions or prerequisites beyond the binary constraint.

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