Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Task-only job (taskSupport: required)

run_task_required
Read-only

Runs a fake multi-step job that must be invoked as an MCP task, enforcing task-support requirements and failing if the client cannot handle task execution.

Instructions

Same fake job as run_task, but declared execution.taskSupport "required": the client must call it as a task. Without task support it fails (-32601 on 2025-era, -32021 on 2026-07-28).

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

Input Schema

NameRequiredDescriptionDefault
stepsNoNumber of steps; each one updates statusMessage
outcomeNosuccess = normal result; tool_error = result with isError (task still "completed"); failure = JSON-RPC error (task "failed")success
secondsNoHow long the fake job runs
askConfirmationNoHalfway through, ask the user to continue (task status input_required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and idempotentHint; the description adds genuinely new behavioral information by disclosing the hard failure modes (-32601 on 2025-era, -32021 on 2026-07-28) that an agent cannot get from structured fields. It stops short of describing task lifecycle behavior, but the failure disclosure is the operationally important part.

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 compact sentences with zero filler; the differentiator is front-loaded and the failure clause follows immediately. Every clause carries information an agent needs.

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?

All four parameters are fully described in the schema and no output schema is needed because the description covers the error outcomes instead. The one residual gap is that the actual task-creation mechanics and result shape are only implied by reference to run_task.

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% and the enum values, defaults and bounds are all documented in the schema, so the baseline applies. The description adds nothing about steps, outcome, seconds or askConfirmation, deferring entirely to the schema via 'same fake job as run_task'.

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 the tool's distinguishing trait precisely: it is the same fake job as run_task but declares execution.taskSupport "required", so the client must invoke it as a task. That is a specific verb/resource plus an explicit contrast to a named sibling. It leans slightly on knowing what run_task does, which keeps it short of 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 Guidelines4/5

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

It states the condition that selects this tool (the client supports and will use task-based invocation) and the consequence of the wrong choice (failure with specific JSON-RPC error codes per protocol era). It does not say what to use instead when task support is absent, though the sibling run_task is strongly implied by the opening clause.

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