Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Toggle Subscriber Updates

toggle-subscriber-updates

Toggle simulated resource subscription updates on or off for 2025-era MCP clients; deprecated for protocol 2026-07-28 in favor of trigger-resource-update with a subscriptions/listen stream.

Instructions

Toggles simulated resource subscription updates on or off. Deprecated: 2025-era clients only, since protocol version 2026-07-28 removes resources/subscribe; use trigger-resource-update with a subscriptions/listen stream 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-subscriber-updates"
  }
}

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 declare readOnlyHint=false and idempotentHint=false, which the description reinforces by describing a state flip ("on or off"); the deprecation and protocol-version rationale are genuinely useful context beyond the structured fields. The gap is that with zero parameters it never explains how the target state is chosen (flip vs. explicit mode), which matters for a non-idempotent toggle.

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, purpose front-loaded, then deprecation and migration guidance. Every clause carries actionable information for an agent deciding whether to call it.

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 deprecated, zero-parameter tool with no output schema, the definition covers purpose, deprecation status, and replacement path. What remains unstated is the observable effect/return of the toggle, a minor gap given no output schema exists.

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?

There are no input parameters, so baseline is 4; the 100% schema coverage is trivially empty and the description adds the relevant behavioral framing instead. The only shortfall is the unexplained mechanism of toggling without an argument.

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 resource subscription updates") with an explicit on/off scope, and names the sibling that supersedes it (trigger-resource-update) so an agent can distinguish the two without opening schemas.

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?

Gives explicit routing: this tool is for 2025-era clients only, and the alternative path (trigger-resource-update with a subscriptions/listen stream) is named along with the reason (protocol version 2026-07-28 removes resources/subscribe). When-to-use and when-to-use-something-else are both present.

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