resolve_drift
Mark drift event as resolved.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| drift_id | No | ||
| resolved_by | No |
driftoracle
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full responsibility for behavioral disclosure. It does not state whether the action is reversible, idempotent, requires special permissions, or affects downstream processes like drift history or health checks.
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?
The description is a single, concise sentence with no filler or repetition. It is front-loaded with the action and subject, making it immediately scannable.
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?
The tool interacts with drift events, but the description omits key context such as what 'resolved' means, whether the resolution is persistent, how it relates to detection or thresholds, and what happens to the drift_id after resolution. With no output schema or annotations, this leaves significant gaps for an agent.
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?
With schema description coverage at 0%, the description must compensate for the undocumented parameters 'drift_id' and 'resolved_by'. The phrase 'Mark drift event as resolved' implies drift_id identifies the event, but it does not clarify the role or required format of 'resolved_by'.
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 'Mark drift event as resolved' uses a specific verb ('mark') and resource ('drift event') with a clear resulting state ('resolved'). It distinguishes itself from sibling tools like detect_drift variants and even 'mark_drift' by specifying the resolved outcome.
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 such as 'mark_drift' or 'trigger_remediation'. There is no mention of prerequisites, sequencing, or when resolving is appropriate versus other actions.
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.