mcptask.online

BlockTaskTool

Block or unblock a task that cannot be completed temporarily

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": {
      "account_code": "<account_code>",
      "task_relative_id": "<task_relative_id>",
      "action": "<action>"
    },
    "name": "BlockTaskTool"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Action to perform: "block" or "unblock"
`reason`	No	Optional reason for blocking or unblocking the task
`account_code`	Yes	Account code (e.g., "bcp", "jchsoft")
`task_relative_id`	Yes	Relative ID of the task to block or unblock

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the safety question is answered structurally. The description adds nothing beyond that: it does not say whether blocking affects downstream tasks, notifies anyone, requires a reason, or is reversible, which are the behavioral facts an agent needs for a state-changing task operation.

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 waste and the action front-loaded. It is slightly under-specified rather than bloated, which is the better failure mode here.

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

Completeness2/5

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

This is a state-mutating tool with no output schema and no annotations describing side effects, yet the description omits what blocking does to the task, its dependents, or the resulting state. The ambiguity against ManageBlockerLinksTool is also left unresolved, leaving real gaps for an agent to guess at.

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%, with the enum and each parameter documented inline, so the schema carries the parameter burden. The description adds no extra semantics (e.g., what a 'reason' is used for or what task_relative_id is relative to), which is the baseline-3 case.

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 states a specific verb pair (block/unblock) and resource (task), so the core action is unambiguous. However, it offers no differentiation from the sibling ManageBlockerLinksTool, which an agent could easily confuse with this one, and the qualifier 'that cannot be completed temporarily' is vague about scope.

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?

There is no guidance on when to block versus unblock, no prerequisites, and no mention of the closely related ManageBlockerLinksTool sibling. The agent must infer usage entirely from the enum in the schema.

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

All mcptask.online tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?