Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Trigger Long Running Operation Tool

trigger-long-running-operation
Read-onlyIdempotent

Starts a configurable long-running operation and reports progress updates, enabling you to test or demonstrate progress-aware workflows through mcp-airlock.

Instructions

Demonstrates a long running operation with progress updates.

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-long-running-operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsNoNumber of steps in the operation
durationNoDuration of the operation in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description does contribute one non-obvious behavioral trait — that progress updates are emitted during execution — but omits whether the call blocks, how progress is delivered, or what is returned at the end.

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?

A single short sentence with no filler, and the key trait (progress updates) is stated immediately. It is efficient, though its brevity is part of why coverage is thin.

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

Completeness3/5

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

With only two fully documented optional parameters and no output schema, the structural burden is light and the description covers the gist. It still leaves the agent unsure about the final return value and whether the tool performs any observable side effect.

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 description coverage is 100%, so both 'steps' and 'duration' already carry their meaning and defaults in the schema. The description adds no additional semantics such as how duration interacts with steps or whether they are approximate.

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

Purpose3/5

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

The description identifies the resource as a long running operation with progress updates, but the verb 'demonstrates' makes the actual effect ambiguous — it is unclear whether anything real is executed or this is purely a sample. Nothing distinguishes it from the many trigger-* siblings.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives among the trigger-* siblings. An agent has to infer that this is a demo/test fixture rather than a functional operation.

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