Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Release Sync

delimit_release_sync
Read-onlyIdempotent

Audit public surface configurations to detect release version drift across CLI, action, npm, and site. Identify inconsistencies before deployment.

Instructions

Audit or report config of public surfaces for consistency (Pro).

When to use: to confirm that all public surfaces (CLI, action, npm, site) reference the same release version and configuration. When NOT to use: to actually deploy or sync content — this is a read/audit tool only.

Sibling contrast: delimit_release_status reports the deployed state; this audits the public surface configuration for drift.

Side effects: gated by require_premium. Calls ai.release_sync.audit (read-only audit) or ai.release_sync.get_release_config when action="config".

Prerequisite: requires Delimit Pro. An unlicensed call returns {"error": ..., "upgrade": "https://delimit.ai/pricing"} without running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoSub-action — "audit" (default) or "config".audit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.7.9
    • addedInput schema / properties / action / description
      Added value: +"Sub-action — \"audit\" (default) or \"config\"."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive hints. The description goes further by disclosing the license gate, naming the internal endpoints (ai.release_sync.audit and ai.release_sync.get_release_config), and specifying the unlicensed response shape. This adds meaningful 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with labeled sections and front-loaded purpose. There is minor redundancy between the initial '(Pro)' marker and the later prerequisite line, but otherwise every section contributes useful information without bloat.

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 single-parameter read-only audit tool with an output schema and comprehensive annotations, the description covers scope, exclusions, sibling distinction, licensing, side effects, and error behavior. Nothing an agent needs to decide whether to call this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the lone parameter's description already documents the 'audit' and 'config' values. The description adds extra meaning by mapping each action to a specific internal endpoint and reinforcing the default behavior, which helps the agent anticipate what happens for each value.

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 opens with a specific verb and resource: 'Audit or report config of public surfaces for consistency.' It explicitly names the surfaces (CLI, action, npm, site) and contrasts with delimit_release_status, so an agent can distinguish it from siblings without opening schemas.

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?

The description provides explicit 'When to use' and 'When NOT to use' guidance, plus a direct sibling contrast: delimit_release_status reports deployed state, while this tool audits config drift. It also states the prerequisite (Delimit Pro) and the unlicensed error behavior.

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