Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Trigger Resource Update Tool

trigger-resource-update
Read-only

Announces that a resource URI has changed by sending a notifications/resources/updated event to subscribed clients, so they can refresh cached resource content.

Instructions

Sends a notifications/resources/updated for a resource URI. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream whose resourceSubscriptions name the URI; a 2025-era client receives it once it has called resources/subscribe for the URI.

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": {
      "uri": "<uri>"
    },
    "name": "trigger-resource-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesThe URI of the resource to announce as updated, e.g. demo://resource/dynamic/text/1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, it discloses the two distinct delivery paths by protocol version and the prerequisite that a legacy client must have called resources/subscribe to receive the notification. That is exactly the kind of behavioral context the annotations (readOnlyHint, idempotentHint=false) cannot convey, and the 'delivered on each subscriptions/listen stream' phrasing is consistent with idempotentHint=false.

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, front-loaded with the action, followed by the delivery semantics. There is no filler, and every clause (protocol version, listen stream, legacy subscribe path) carries information the agent needs to predict the effect of the call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter notification tool with no output schema, the description covers what is emitted and under which conditions the emission reaches recipients. Nothing an agent would need to call it correctly 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 coverage is 100% and the schema already provides a concrete example URI, so the parameter is fully documented in structured form. The description only restates 'for a resource URI' and adds no format, constraint, or matching rules beyond the schema; baseline 3 applies.

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?

The description names a concrete verb and payload: it 'sends a notifications/resources/updated for a resource URI', which is specific enough that an agent knows exactly what wire-level action occurs even against similarly named siblings like trigger-list-changed. It does not explicitly contrast itself with those siblings, which keeps it out of the top band, but the notification name itself acts as a disambiguator.

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 description explains delivery conditions (protocol 2026-07-28 listen-stream subscriptions vs. 2025-era clients needing resources/subscribe) but never states the triggering condition for calling it, such as 'use when resource content has changed'. Usage is implied by the resource URI argument rather than instructed, and no alternatives or when-not cases are named.

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