Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Drift Check

delimit_drift_check
Read-onlyIdempotent

Monitor API spec drift against the last governance review to catch unauthorized changes, stale baselines, or missing policy. Use as a scheduled compliance check.

Instructions

Check for API spec drift since last governance review.

When to use: as a scheduled (cron) compliance monitor — detects spec changes without lint, stale baseline, or missing policy. When NOT to use: for one-shot lint (use delimit_lint) or to read historical drift (delimit_drift_history).

Sibling contrast: delimit_lint is enforcement; delimit_drift_history reads past drift records; this is the periodic monitor.

Side effects: read-only on spec + governance state. Calls ai.drift_monitor.check_drift.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spec_pathNoOpenAPI spec path. Empty = auto-detect.
project_pathNoProject root. Default "." (cwd)..
staleness_daysNoAlert if baseline older than this. Default 7.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.7.9
    • changedInput schema / properties / project_path / description
      Previous value: -"Project root. Defaults to current directory."New value: +"Project root. Default \".\" (cwd)."
    • changedInput schema / properties / spec_path / description
      Previous value: -"Path to OpenAPI spec. Auto-detects if empty."New value: +"OpenAPI spec path. Empty = auto-detect."
    • changedInput schema / properties / staleness_days / description
      Previous value: -"Alert if baseline older than this (default 7)."New value: +"Alert if baseline older than this. Default 7."
  2. Addedv4.5.5

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Side effects: read-only on spec + governance state.' It also adds transparency about the underlying call to ai.drift_monitor.check_drift, which is useful behavioral context beyond the annotations.

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 well-structured with clear sections: primary purpose, when to use, when not to use, sibling contrast, and side effects. Every section adds distinct value, and the core statement is front-loaded.

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

Completeness5/5

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

For a tool with optional parameters, full schema coverage, an output schema, and read-only annotations, the description provides all necessary operational context: trigger context, exclusions, sibling relationships, and side effects. Nothing critical is missing for an agent to invoke it correctly.

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?

Input schema has 100% description coverage for all three parameters, so the description is not required to repeat parameter meanings. It adds some contextual value by mentioning 'stale baseline,' which relates to staleness_days, but does not meaningfully expand on the schema's parameter documentation.

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 clearly states the tool's purpose: 'Check for API spec drift since last governance review.' It identifies the specific resource (API spec drift) and distinguishes itself from siblings delimit_lint and delimit_drift_history, making selection unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit when-to-use guidance ('scheduled (cron) compliance monitor') and when-not-to-use guidance ('one-shot lint' and 'historical drift'), naming the exact alternative tools. This fully orients an agent for correct tool selection.

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

Deploy Server

Other Tools