Skip to main content
Glama
Sign In
subtask

subtask

by tedin7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

steer

Correct a background job by sending a hint, aborting it, or retrying with a fresh instruction to keep agent work on track.

Instructions

Correct a job: hint (instruction sent when the attempt ends) | abort | retry (fresh job with the instruction).

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": {
      "id": "<id>",
      "action": "<action>"
    },
    "name": "steer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
actionYes
instructionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that hint sends an instruction when the attempt ends and that retry starts a fresh job with the instruction, but it leaves abort semantics, state effects, and permissions unstated.

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?

The definition is compact and front-loaded, with no redundant wording. The pipe-separated action list is terse but readable.

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?

For a three-parameter job-control tool with no annotations and no output schema, the description covers the central action semantics but omits important context about id, abort behavior, and outcomes. It is adequate but incomplete.

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 0%, so the description must compensate. It clarifies the action values and the role of instruction, but does not define the required id parameter or explain when instruction is required or ignored.

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 resource and set of operations: it corrects a job via hint, abort, or retry. This is clearer than a tautology, but it does not explicitly distinguish itself from nearby tools such as stop or reply.

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?

The description implies usage when a job needs correction, but it gives no explicit when-to-use guidance, prerequisites, or comparison with alternatives. The action list explains mechanics rather than routing.

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