Skip to main content
Glama
Sign In
io.github.RohitYajee8076/backburner

io.github.RohitYajee8076/backburner

by RohitYajee8076
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

task_status

Check the status of a background task by its ID. Determine if it is working, completed, failed, cancelled, timed out, or interrupted.

Instructions

Check on a task: working, completed, failed, cancelled, timed_out, or interrupted.

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": {
      "task_id": "<task_id>"
    },
    "name": "task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It lists possible statuses but does not disclose whether the operation is read-only, error behavior, auth requirements, or what the response structure looks like.

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?

Single sentence, front-loaded, every word earns its place; no wasted text.

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?

The enumeration of statuses provides useful behavioral context, but missing usage guidance, return format, and error handling leaves gaps. For a single-parameter tool with no output schema and no annotations, this is minimally adequate but not complete.

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?

The sole parameter task_id is not mentioned in the description beyond the implicit 'task'. Schema description coverage is 0%, and the description does not clarify the format, requiredness, or source of task_id.

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 the verb 'check' with 'task' as the resource and enumerates six possible statuses, making its purpose clear. It differentiates from siblings like start_task and cancel_task, though it doesn't explicitly name alternatives.

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 explicit guidance on when to use this tool versus task_result or list_tasks. The status list implies usage but there are no exclusions or alternative recommendations.

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

Deploy Server

Other Tools