Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Toggle Simulated Logging

toggle-simulated-logging

Toggles simulated random-level logging on or off for 2025-era MCP clients, a legacy alternative for testing log output before protocol 2026-07-28 removed logging/setLevel.

Instructions

Toggles simulated, random-leveled logging on or off. Deprecated: 2025-era clients only, since protocol version 2026-07-28 removes logging/setLevel; use trigger-log-messages with a per-request log level instead.

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": "toggle-simulated-logging"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the mutation safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's job is narrower. It adds genuine behavior beyond that: the log levels produced are simulated and randomly leveled, and the tool is deprecated because the underlying protocol method is being removed. It does not say whether calling it returns the resulting state, which is the only remaining gap.

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?

Two sentences, zero waste. The functional statement comes first and the deprecation/routing guidance follows, which is the correct priority for an agent deciding whether to call it at all.

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 zero-parameter, annotation-covered toggle with no output schema, the definition covers purpose, deprecation, and the migration path. Only the return behavior (whether the new on/off state is reported) is left unstated, a minor omission at this complexity level.

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 input schema has zero parameters, so there is no parameter meaning to add or omit; the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

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

Purpose5/5

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

States a specific verb and resource ('Toggles simulated, random-leveled logging') and immediately distinguishes the tool's positioning by marking it deprecated in favor of a named sibling. An agent can tell what it does and what supersedes it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly scopes usage to '2025-era clients only' and names the replacement ('use trigger-log-messages with a per-request log level instead'), including the reason (protocol version 2026-07-28 removes logging/setLevel). When-to-use, when-not-to-use, and the alternative are all present.

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