Skip to main content
Glama

dismiss supervisor task

dismiss_supervisor_task

Dismiss an incident after a human confirms no repair is needed, closing the supervisor task by job ID. Requires a write-scope key.

Instructions

Dismiss an incident after a human decides no repair is needed. Requires a write-scope key.

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": {
      "jobId": "<jobId>"
    },
    "name": "dismiss_supervisor_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose a required 'write-scope key' and the human-decision precondition. It omits what dismissal does to the task's state, whether it is reversible, and whether downstream steps are affected — significant gaps for a mutation operation.

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 short sentences with zero waste; the purpose is front-loaded and the prerequisite follows immediately. Nothing 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?

For a single-parameter mutation with no annotations and no output schema, the description covers purpose, precondition, and auth scope, which is a reasonable minimum. It is not complete enough to guarantee a correct call because the jobId's origin and the effect of dismissal are left unexplained.

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?

There is one parameter (jobId) with 0% schema description coverage, and the description never mentions it or explains which incident identifier to pass. The schema only constrains it to a positive integer, so an agent must guess where the id comes from (e.g., list_supervisor_queue or get_supervisor_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?

States a specific verb (dismiss) plus the object (an incident/supervisor task) and the precondition under which it applies. It is distinguishable from sibling operations like apply_supervisor_task or release_supervisor_task by the 'no repair is needed' semantics, though no sibling is named explicitly.

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?

Gives an implicit when-to-use condition ('after a human decides no repair is needed'), which is genuinely useful decision context. It does not say when NOT to use it, nor does it point to an alternative such as apply_supervisor_task when repair is needed, so routing remains partly inferred.

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