configure_thresholds
View/set drift detection thresholds.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| set | No | True to update | |
| evidence_max_age_days | No | ||
| assessment_max_age_days | No |
driftoracle
TDQS
C2.9/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 burden of behavioral transparency. It only states 'View/set' without disclosing side effects, persistence, reversibility, permissions, or whether setting thresholds overwrites existing values. This is insufficient for a mutation-capable tool.
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 description is extremely concise with no wasted words, and the key action is front-loaded. However, it may be too terse for the tool's parameter count, though that is more a completeness concern than a conciseness issue.
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?
Given no annotations, no output schema, and 3 parameters, the description is not complete enough for an agent to invoke correctly. It omits how 'set' toggles behavior, whether parameters are required together, and what return or side effects to expect.
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 low at 33%, and the description does little to compensate. It vaguely references 'thresholds' but does not explain the 'set' boolean or the two max_age_days parameters, leaving their semantics largely to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'View/set drift detection thresholds' uses a specific verb and resource, clearly communicating both read and write capabilities. It distinguishes itself from sibling tools like detect_drift and drift_status by focusing on configuration of thresholds.
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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or scenarios where configuring thresholds is appropriate versus using the various drift detection/history tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.8/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, with detection tools differentiated by drift type. Minor overlap exists between health_check and ping, as well as control_drift and evidence_drift sharing degraded controls, but descriptions provide enough context to avoid confusion.
Naming Consistency3/5
The naming pattern is mixed: detect_* tools consistently use verb_noun, but drift_history and drift_status follow noun_noun, and full_drift_scan is a compound noun. While readable, the inconsistency makes the set feel less cohesive.
Tool Count4/5
15 tools is slightly above average but justified by the broad scope of drift detection and management. Each tool earns its place, covering detection, viewing, configuration, and remediation without obvious redundancy.
Completeness4/5
The tool set covers the full drift lifecycle: detection (multiple types), full scan, history, status, configuration, manual marking/resolving, and automated remediation. Minor gaps like lacking a single-event detail view are not critical for core workflows.