Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Trigger List Changed Tool

trigger-list-changed
Read-only

Announce changes to MCP tool, prompt, or resource lists by sending list_changed notifications to subscribed listeners or 2025-era clients.

Instructions

Sends a notifications//list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list": "<list>"
    },
    "name": "trigger-list-changed"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYesWhich list to announce as changed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing delivery semantics that matter: on 2026-07-28 protocol it is delivered per subscriptions/listen stream that subscribed to that list, whereas a 2025-era client receives it unsolicited. This is useful non-obvious behavior that annotations (readOnlyHint true, idempotentHint false, openWorldHint false) do not convey. It omits failure modes and what happens if no stream is listening.

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 tight sentences, front-loaded with the action and notification shape, followed by the version-dependent delivery behavior. No filler, though the protocol-version clause is dense and could be split for readability.

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 one-parameter, no-output-schema tool with annotations covering safety, the description supplies the key behavioral context (what is emitted and how it is delivered across protocol versions). Only error/no-subscriber behavior is left unstated, a minor gap.

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?

The schema already documents the single 'list' parameter at 100% coverage, including an enum of tools/prompts/resources, and the description adds no format or selection guidance beyond that. Baseline 3 applies where the schema does the heavy lifting.

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?

Names a specific verb ('Sends a notifications/<list>/list_changed') and the exact resource/scope (tool, prompt, or resource list), so an agent can tell it apart from per-resource siblings like trigger-resource-update. It stops short of explicitly naming or contrasting any sibling, so it does not reach a 5.

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 only implied: an agent can infer it should call this when a cached list should be re-announced, but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. No prerequisites or exclusions are stated.

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