Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Trigger Log Messages Tool

trigger-log-messages
Read-onlyIdempotent

Sends one log message at each logging level to verify which severity levels are emitted under the client's protocol version and log-level settings.

Instructions

Sends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.

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": "trigger-log-messages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the filtering semantics: which messages are emitted depends on protocol version and on the level named in _meta (io.modelcontextprotocol/logLevel) or on logging/setLevel for 2025-era clients, with none sent if no level is named. The annotations already cover the read-only/idempotent/non-destructive profile, so this added delivery logic is genuine value; only the response shape is left unstated.

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?

Three sentences, front-loaded with the action before the version-conditional detail, and no filler. The version paragraph is dense but every clause carries a distinct rule an agent needs.

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?

With zero parameters, no output schema, and annotations already declaring safety, the definition covers what the agent needs to decide and call. The one gap is whether the messages surface as client notifications versus in the call result, which matters for interpreting the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4, and the description usefully explains the out-of-band _meta logLevel key that governs behavior even though it is not in the input schema. That is meaning the schema alone would not convey.

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: 'Sends one log message at each logging level during the call.' This is concrete enough that an agent knows exactly what invocation produces, though it never contrasts itself with the nearby toggle-simulated-logging sibling.

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 deprecation sentence is a real usage signal (avoid relying on this, logging is deprecated as of 2026-07-28), but no replacement tool is named and there is no explicit when-to-use/when-not framing beyond that. The version-conditional delivery rules imply this is a test/probe tool without saying so.

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