Skip to main content
Glama

set_confidence_threshold

Set a confidence threshold so alerts trigger when worker confidence falls below it during autonomous coding sessions.

Instructions

Configure the confidence threshold for alerts. When worker confidence drops below this threshold, alerts will be generated.

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>",
      "threshold": "<threshold>"
    },
    "name": "set_confidence_threshold"
  }
}

Input Schema

NameRequiredDescriptionDefault
autoAlertNoAutomatically log alerts to progress log (default: true)
thresholdYesConfidence threshold (0-100, default: 35)
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the downstream alert-generation behavior, which is genuinely useful, but says nothing about persistence scope (per-project vs global), whether changes apply to in-flight workers, whether existing alerts are affected, or what permissions/auth are required for this mutation.

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 filler, and the core purpose is front-loaded ahead of the mechanism. Nothing could be cut without losing information.

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 mutation tool with no output schema and no annotations, the definition covers the what and the effect but leaves the operational context under-specified: no note on persistence, scope, or idempotence of repeated configuration.

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%, so all three parameters are already documented, establishing a baseline of 3. The description adds clarifying meaning for 'threshold' (below it, alerts fire) but says nothing about autoAlert or projectDir beyond the schema.

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?

Uses a specific verb+resource ("Configure the confidence threshold for alerts") and immediately explains what the threshold does. An agent can distinguish this from the getter sibling get_worker_confidence without opening either schema, 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?

The description implies when the setting matters (worker confidence dropping below the threshold triggers alerts) but gives no explicit when-to-use, prerequisites, or when-not guidance relative to siblings like get_worker_confidence or the other configure_* tools.

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