Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

airlock_report

Returns a live audit summary of allowed and blocked calls, top tools, block reasons, and recent errors so you can monitor MCP governance.

Instructions

Return a live audit summary from Airlock: total/allowed/blocked calls, top tools, block reasons and recent errors. Injected by the local governance proxy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "airlock_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows per breakdown (default 10).
session_onlyNoOnly count calls from the current session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 full behavioral burden; it discloses that the data is live and lists the return dimensions, which is useful. It does not explicitly confirm read-only behavior, permissions, rate limits, or pagination, leaving meaningful gaps.

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?

A single front-loaded sentence with no wasted wording that both states the action and enumerates the returned content. The provenance note about the governance proxy is compact and earns its place.

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 low-complexity, zero-required-parameter reporting tool with no output schema, the description sufficiently covers the return dimensions and the live/injected nature of the data. It could say more about read-only guarantees or response shape, but nothing essential is missing.

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 both parameters (limit and session_only) are already documented in the input schema. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline 3 appropriate.

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: 'Return a live audit summary from Airlock', then enumerates the metrics included (allowed/blocked calls, top tools, block reasons, recent errors). This clearly distinguishes it from the generic echo/utilization siblings, 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?

Usage is implied by 'live audit summary' and the mention that it is injected by the local governance proxy, which signals a diagnostics/governance context. It does not state when to prefer it over alternatives or any exclusions, but the sibling set contains no comparable audit tool.

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