Skip to main content
Glama

delimit_drift_check

Monitors API specifications for drift since the last governance review, ensuring compliance by detecting changes without lint or policy files.

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

Behavior4/5

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

No annotations provided, but description states side effects are read-only on spec and governance state, and mentions underlying API call. Lacks detail on return format or error conditions, but sufficient for a non-destructive tool.

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?

Description is concise and well-structured with clear sections for purpose, usage, exclusions, sibling contrast, and side effects. No unnecessary words.

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?

Given the tool's simplicity (3 optional params, output schema exists), the description covers purpose, usage, side effects, and alternatives adequately for an agent to select and invoke it.

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% with descriptions and defaults. Description adds minimal extra meaning beyond schema, so baseline 3 is appropriate.

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?

Description clearly states the tool checks for API spec drift since last governance review. It uses a specific verb (check) and resource (drift). It also distinguishes from siblings by explicitly contrasting with delimit_lint and delimit_drift_history.

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 guidance: when to use (scheduled cron compliance monitor) and when not (one-shot lint or historical drift). Names alternatives: delimit_lint and delimit_drift_history.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delimit-ai/delimit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server