Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Os Gates

delimit_os_gates
Read-onlyIdempotent

Check if a specific OS plan is blocked by governance gates before proceeding. Returns gate state for a single plan using its plan ID.

Instructions

Check governance gates for an OS plan (Pro).

When to use: to check whether a specific plan is currently blocked by a governance gate before proceeding. When NOT to use: for general OS counts (use delimit_os_status) or governance engine health (delimit_gov_health).

Sibling contrast: delimit_os_status returns aggregate counts; delimit_gov_health reports the engine; this returns gate state for one plan.

Side effects: read-only on the OS backend; gated by require_premium. Calls backends.os_bridge.check_gates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYesPlan identifier, e.g. "PLAN-A1B2C3D4". Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.7.9
    • changedInput schema / properties / plan_id / description
      Previous value: -"The plan ID (e.g. \"PLAN-A1B2C3D4\")."New value: +"Plan identifier, e.g. \"PLAN-A1B2C3D4\". Required."
  2. Changed1 schema field changedv4.5.5
    • addedInput schema / properties / plan_id / description
      Added value: +"The plan ID (e.g. \"PLAN-A1B2C3D4\")."
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that the operation is read-only on the OS backend, is gated by require_premium, and calls backends.os_bridge.check_gates. This adds meaningful behavioral context such as authorization requirements and backend coupling.

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 efficiently organized with clear sections: core purpose, when to use, when not to use, sibling contrast, and side effects. Every sentence contributes useful decision-making information without redundancy.

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 annotations cover read-only/idempotent behavior, the schema covers the sole parameter, the output schema exists, and the description provides usage guidance plus authorization and side-effect context, the tool definition is complete for an agent to invoke 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?

Schema coverage for the single parameter is 100%, so the schema already documents plan_id. The description adds minimal semantic value beyond noting it checks a 'specific plan,' which is sufficient given the complete 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 states a specific verb and resource: 'Check governance gates for an OS plan (Pro).' It clearly distinguishes the tool from siblings by noting it 'returns gate state for one plan' versus aggregate counts or engine health.

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 gives explicit when-to-use ('to check whether a specific plan is currently blocked by a governance gate before proceeding'), when-not-to-use, and names the specific alternatives (delimit_os_status, delimit_gov_health). This leaves no ambiguity about 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