Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Slow task (progress, logs, cancellation)

slow_task
Read-only

Simulates a long-running task that reports progress and log messages, and supports early cancellation by the client.

Instructions

Run a fake long task that reports progress notifications and log messages, and stops early when the client cancels it.

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": "slow_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsNo
delayMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, which is consistent with the 'fake' task framing. The description adds useful behavioral detail beyond the annotations – it emits progress notifications and log messages, and terminates early when the client cancels – but says nothing about how cancellation is signalled, what the final result looks like, or timing implications of the delay.

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?

A single front-loaded sentence with no filler; purpose and key behaviors (progress, logs, cancellation) all arrive immediately. Nothing here is redundant or padded.

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?

No output schema exists and both parameters are undocumented anywhere, so the description carries the burden of explaining what the tool returns and what the parameters control; it covers the behavioral shape but leaves return values and parameter effects unaddressed. For a demo tool of modest complexity this is adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the two parameters (steps and delayMs), so it adds no meaning beyond the raw schema types and defaults. With defaults of 10 steps and 500ms per step, an agent gets no guidance on how these shape runtime or output.

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 uses a specific verb and resource ('Run a fake long task') and explains what the task produces: progress notifications and log messages. It does not explicitly distinguish itself from sibling tools like run_task or run_task_required, so an agent must infer the difference from the word 'fake', which keeps it below 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 implied rather than stated: by describing a fake task that emits progress and logs and honors cancellation, it suggests the tool is for exercising client-side progress/cancellation handling. There is no explicit when-to-use, when-not-to-use, or naming of the real-task alternatives, leaving the agent to infer.

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