Skip to main content
Glama

get_worker_confidence

Retrieves confidence analysis for a running worker, showing tool activity patterns, self-reported confidence, and output analysis to assess how reliably a feature worker is progressing.

Instructions

Get detailed confidence analysis for a running worker. Shows tool activity patterns, self-reported confidence, and output analysis.

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": {
      "projectDir": "<projectDir>",
      "featureId": "<featureId>"
    },
    "name": "get_worker_confidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
featureIdYesID of the feature whose worker to analyze
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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. 'Get' plus the analytical framing make it clear this is a read-only inspection, and the description discloses the categories of information returned. However, nothing is said about behavior if the worker is not running, whether the analysis is live or cached, latency/cost, or whether any state is affected.

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?

Two short sentences, front-loaded with the verb and target, with the returned content listed second. There is minor redundancy between 'confidence analysis' and 'self-reported confidence', but every sentence contributes.

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

Completeness4/5

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

This is a low-complexity two-parameter read tool with no output schema, and the description compensates by enumerating the three kinds of information returned. The main remaining gap is the failure mode when no running worker matches the given featureId, which an agent would need to know.

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% and both parameters (projectDir, featureId) are already documented in the schema. The description adds only indirect meaning — that the identified worker must be running for the call to be meaningful — so per the baseline rule a 3 is appropriate.

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 a specific verb+resource ('Get detailed confidence analysis for a running worker') and then enumerates what the analysis covers: tool activity patterns, self-reported confidence, and output analysis. This makes the tool distinguishable from generic status getters like check_worker, though it never explicitly contrasts itself with them.

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?

The phrase 'for a running worker' implies a precondition (the worker must be running) and thus a usage context, but there is no explicit when-to-use guidance, no exclusions, and no named alternative such as check_worker or get_session_stats for coarser status checks. Usage is inferable but not stated.

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