Skip to main content
Glama

report supervisor task

report_supervisor_task

Queues an observed problem, including incomplete page loads missed by automated detection, so supervisors can review and act on it; requires a write-scope key.

Instructions

Queue an observed problem, including incomplete loads missed by automated detection. 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>",
      "reason": "<reason>"
    },
    "name": "report_supervisor_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
reasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important behavioral fact: a write-scope key is required, indicating a privileged mutation rather than a read. It does not say what happens after queueing, whether duplicate reports are merged, or what the caller gets back, leaving substantial behavioral gaps.

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 the action front-loaded and the prerequisite stated second; every clause contributes information and nothing is padded.

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 mutation tool with no annotations, no output schema, and two undocumented required parameters, yet the description explains neither the jobId reference nor the outcome of queueing. It states the minimum to guess at intent but not enough to invoke correctly.

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?

Schema description coverage is 0% for two required parameters, so the description must compensate but does not. It never explains what 'jobId' identifies or constrains 'reason' beyond the schema's length limits, and the mention of 'incomplete loads' only loosely hints at reason content.

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 gives a specific verb and object ('Queue an observed problem') and clarifies the tool's domain with 'including incomplete loads missed by automated detection,' so an agent understands this files a supervisor task about an observed issue. It does not differentiate itself from the many other supervisor_task siblings (apply, claim, dismiss, etc.), which keeps it below 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 Guidelines3/5

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

A use case is implied through 'observed problem, including incomplete loads missed by automated detection,' which tells the agent this is for reporting issues that automation did not catch. There is no explicit when-not guidance and no named alternative among the sibling tools.

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