Skip to main content
Glama
crunchtools

io.github.crunchtools/airlock

Official
by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search Tool

search_tool

Search the web securely to get a grounded answer and sources. Follow up with fetch_tool for safe content extraction.

Instructions

Search the web; the grounded answer, titles and URLs are judged as one.

Returns the answer plus the sources, which can be followed up with fetch_tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string
num_resultsNoApproximate number of results (default 5)
trentina_modeNoblock, flag, or {"redact": "<what you need>"}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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>\"}"
    • 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

B3.2/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 behavioral burden. It offers one cryptic signal ('answer, titles and URLs are judged as one') that never explains what that means operationally, and it says nothing about the strange trentina_mode behavior (block/flag/redact), rate limits, or grounding guarantees. Significant gaps for an unannotated tool.

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 with the core action front-loaded and the follow-up workflow second. Minimal waste, though the opening clause about results being 'judged as one' is murky enough to dilute the conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, which lightens the load. But given the cryptic trentina_mode parameter and zero annotations, the description leaves real behavioral questions unanswered for a tool with a non-obvious configuration surface. Minimum viable, not complete.

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 query, num_results, and trentina_mode, making the baseline 3. The description adds nothing about parameters and does not clarify the opaque 'block, flag, or {"redact": ...}' modes. It neither helps nor harms beyond the schema baseline.

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 and resource ('Search the web') and clarifies the return shape (grounded answer plus sources). It gestures at sibling differentiation by naming fetch_tool as the follow-up step, though it does not contrast itself with read_tool or content_tool. Clear and distinguishable, but sibling routing is only partially resolved.

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 phrase 'can be followed up with fetch_tool' implies a search-then-fetch workflow, which hints at when this tool is the entry point. However, there is no explicit when-not condition and no contrast with the other retrieval siblings (read_tool, content_tool). Usage is implied rather than stated.

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