Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Delimit Policy

delimit_policy
Read-onlyIdempotent

Inspect or simulate governance policy configuration. Dry-run lint and policy presets to preview what would block before enforcing.

Instructions

Inspect or simulate governance policy configuration.

When to use: to inspect the active policy or dry-run lint+policy against several presets to preview what would block. When NOT to use: for an actual gate decision (use delimit_lint) or to manage the policy file itself (delimit_gov_policy).

Sibling contrast: delimit_gov_policy reads the live policy; delimit_lint enforces; this lets you simulate / inspect.

Side effects: read-only on policy + spec files. action="simulate" runs lint internally without writing evidence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo"inspect" (default) or "simulate".inspect
new_specNoProposed spec path (required for simulate).
old_specNoBaseline spec path (required for simulate).
spec_filesYesList of spec file paths. Required.
policy_fileNoOptional custom policy file path.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv4.7.9
    • changedInput schema / properties / action / description
      Previous value: -"\"inspect\" or \"simulate\"."New value: +"\"inspect\" (default) or \"simulate\"."
    • changedInput schema / properties / new_spec / description
      Previous value: -"Path to proposed spec (required for simulate)."New value: +"Proposed spec path (required for simulate)."
    • changedInput schema / properties / old_spec / description
      Previous value: -"Path to baseline spec (required for simulate)."New value: +"Baseline spec path (required for simulate)."
    • changedInput schema / properties / spec_files / description
      Previous value: -"List of spec file paths."New value: +"List of spec file paths. Required."
  2. Changed5 schema fields changedv4.5.5
    • addedInput schema / properties / action
      Added value: +{
+  "default": "inspect",
+  "description": "\"inspect\" or \"simulate\".",
+  "type": "string"
+}
    • addedInput schema / properties / new_spec
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Path to proposed spec (required for simulate)."
+}
    • addedInput schema / properties / old_spec
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Path to baseline spec (required for simulate)."
+}
    • addedInput schema / properties / policy_file / description
      Added value: +"Optional custom policy file path."
    • addedInput schema / properties / spec_files / description
      Added value: +"List of spec file paths."
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Although annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, the description adds valuable specifics: 'read-only on policy + spec files' and 'action="simulate" runs lint internally without writing evidence.' This goes beyond the annotations and clarifies the practical safety profile.

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 compact and front-loaded with the core purpose, then organized into clear when/when-not, sibling contrast, and side effects sections. Every sentence adds useful 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?

For a tool with five parameters, a rich annotation set, an output schema, and many siblings, the description covers purpose, usage boundaries, side effects, and alternatives. Nothing crucial is missing for an agent to select and invoke the tool correctly.

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 description coverage is 100%, so the schema already documents all five parameters. The description adds meaning beyond the schema by explaining that action='simulate' runs lint internally, which clarifies what the action parameter actually does in practice.

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 'Inspect or simulate governance policy configuration,' a specific verb+resource statement. It also distinguishes itself from delimit_gov_policy and delimit_lint via explicit sibling contrast, so an agent can tell exactly what this tool does.

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 explicitly provides 'When to use' and 'When NOT to use' sections, naming the exact alternative tools (delimit_lint, delimit_gov_policy) and the conditions that select them. No inference is required.

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