Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Gov Verify

delimit_gov_verify

Attest that a completed governance task satisfies policy, producing an audit-ready verification record. Use after execution to flip status from ran to verified.

Instructions

Attest that a governance task completed under policy (Pro).

When to use: as step three (closing step) of the governance pipeline, immediately after delimit_gov_run has recorded the execution. This is the call that flips a task from "ran" to "verified" and produces the attestation entry used by downstream audit consumers. When NOT to use: to mint a task (delimit_gov_new_task) or to record the execution itself (delimit_gov_run). Verify is closing only — it does not run work and does not create tasks.

Sibling contrast: delimit_gov_new_task creates; delimit_gov_run records execution; this attests the outputs satisfy policy. Compared to delimit_evidence_verify (which checks an evidence file), this attests against the policy engine, not a static file.

Side effects: gated by require_premium — unlicensed callers receive a license payload, no verification recorded. On a licensed call, invokes backends.governance_bridge.verify which writes a verification record against the task_id (verdict, timestamp, repo, policy snapshot). The response is routed through _with_next_steps. Does not perform additional work — only validates and records the verdict.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNoFilesystem path to the repository. Default "." (cwd)..
task_idNoIdentifier from delimit_gov_new_task / delimit_gov_run. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.7.9
    • addedInput schema / properties / repo / description
      Added value: +"Filesystem path to the repository. Default \".\" (cwd)."
    • addedInput schema / properties / task_id / description
      Added value: +"Identifier from delimit_gov_new_task / delimit_gov_run. Required."
  2. Changed2 schema fields changedv4.5.5
    • addedInput schema / properties / task_id / default
      Added value: +""
    • removedInput schema / required
      Removed value: -[
-  "task_id"
-]
  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?

The description goes well beyond the sparse annotations by disclosing side effects: it writes a verification record, is gated by require_premium, behaves differently for unlicensed callers, invokes a specific backend method, and does not perform additional work. It also explains the unlicensed response shape and prerequisite, giving full transparency about what happens when the tool is called.

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 long but well-structured with clear sections for when to use, when not to use, sibling contrast, side effects, and prerequisites. Every section provides actionable information, and the most important usage guidance 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?

The description covers the tool's role in the pipeline, prerequisites, licensing behavior, side effects, backend invocation, and relationship to sibling tools. With an output schema already present, the description does not need to explain return values, and nothing essential is missing for an agent to invoke this 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 coverage is 100%, so the baseline is 3, but the description adds meaningful context by clarifying that task_id is required despite having a default empty string, and that it comes from delimit_gov_new_task / delimit_gov_run. This resolves a potential ambiguity in the input schema where no parameters are marked required.

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: 'Attest that a governance task completed under policy.' It clearly defines the tool's role as the closing verification step in the governance pipeline and distinguishes it from related siblings by explaining that it flips a task from 'ran' to 'verified' and produces an attestation entry.

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 states when to use the tool ('step three, immediately after delimit_gov_run'), when NOT to use it (for minting tasks or recording execution), and names the exact alternatives (delimit_gov_new_task, delimit_gov_run, delimit_evidence_verify). This gives an agent clear routing guidance with no inference required.

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