Skip to main content
Glama

Delimit Gov Impl

_delimit_gov_impl
Read-onlyIdempotent

Dispatch any governance action—health, status, policy, evaluate, new_task, run, or verify—from one entry point, with license gating and deterministic error responses.

Instructions

Unified governance entry point — dispatches to one of seven actions.

When to use: as the single MCP-registered governance surface (delimit_gov) when the caller wants to pick the action by name in one call rather than choosing a specific delimit_gov_* alias. When NOT to use: from internal code paths — prefer the specific alias (delimit_gov_health, delimit_gov_evaluate, etc.) for clarity and so docstrings and license gates show up at the right call site.

Sibling contrast: each delimit_gov_ wrapper above is a thin alias over this implementation; they exist so the action's docstring lives at the right name. This is the dispatch core.

Side effects: action="health" / "status" are read-only and not gated. action="policy" / "evaluate" / "new_task" / "run" / "verify" are gated by require_premium — unlicensed callers receive a license payload and no backend call is made. Each gated action routes to a distinct backends.governance_bridge function (health, status, policy, evaluate_trigger, new_task, run_task, verify) and the result is wrapped via _with_next_steps for orchestrator hints. Errors are deterministic ({"error": ...}); inputs that cannot be coerced (e.g. malformed context for evaluate) short-circuit before the backend call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNoRepository path. Default "." (cwd)..
scopeNoTask scope (used only when action="new_task"). Required for new_task.
titleNoTask title (used only when action="new_task"). Required for new_task.
actionNoWhich governance operation to perform. One of "health", "status", "policy", "evaluate", "new_task", "run", "verify". Default "health". Other values return a deterministic error.health
contextNoAdditional context (used only when action="evaluate"). Strings are auto-coerced to {"text": ...} via _coerce_dict_arg; dicts are passed through. None is allowed.
task_idNoTask ID (used only when action="run" or action="verify"). Required for those actions.
risk_levelNoRisk level low/medium/high/critical (used only when action="new_task"). Default "medium".medium
eval_actionNoThe proposed action name to evaluate (used only when action="evaluate"). Empty string is rejected by the backend.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed8 schema fields changedv4.7.9
    • changedInput schema / properties / action / description
      Previous value: -"Which governance operation to perform."New value: +"Which governance operation to perform. One of \"health\",\n\"status\", \"policy\", \"evaluate\", \"new_task\", \"run\",\n\"verify\". Default \"health\". Other values return a\ndeterministic error."
    • changedInput schema / properties / context / description
      Previous value: -"Additional context (for action='evaluate')."New value: +"Additional context (used only when action=\"evaluate\").\nStrings are auto-coerced to {\"text\": ...} via\n_coerce_dict_arg; dicts are passed through. None is\nallowed."
    • changedInput schema / properties / eval_action / description
      Previous value: -"The action to evaluate (for action='evaluate')."New value: +"The proposed action name to evaluate (used only\nwhen action=\"evaluate\"). Empty string is rejected by the\nbackend."
    • changedInput schema / properties / repo / description
      Previous value: -"Repository path."New value: +"Repository path. Default \".\" (cwd)."
    • changedInput schema / properties / risk_level / description
      Previous value: -"Risk level low/medium/high/critical (for action='new_task')."New value: +"Risk level low/medium/high/critical (used only when\naction=\"new_task\"). Default \"medium\"."
    • changedInput schema / properties / scope / description
      Previous value: -"Task scope (for action='new_task')."New value: +"Task scope (used only when action=\"new_task\"). Required\nfor new_task."
    • changedInput schema / properties / task_id / description
      Previous value: -"Task ID (for action='run' or action='verify')."New value: +"Task ID (used only when action=\"run\" or\naction=\"verify\"). Required for those actions."
    • changedInput schema / properties / title / description
      Previous value: -"Task title (for action='new_task')."New value: +"Task title (used only when action=\"new_task\"). Required\nfor new_task."
  2. Addedv4.5.5

TDQS

A3.7/5.0
Behavior1/5

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

The prose is rich, disclosing gating, per-action backend routing, deterministic errors, and _with_next_steps wrapping. However, it directly contradicts the readOnlyHint:true annotation by explicitly stating that only action='health' and action='status' are read-only, implying the other actions are not. Per the rubric, a description that contradicts annotations must receive a score of 1 and be flagged as an annotation contradiction.

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 long but well-structured with clear headings for usage, non-usage, sibling contrast, and side effects. It is front-loaded with the core purpose and each section carries meaningful information for a seven-action dispatcher. Minor redundancy exists between the sibling contrast section and the when-to-use/when-not-to-use paragraphs, preventing a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with seven actions, eight parameters, and nontrivial routing, the description covers selection criteria, exclusions, per-action side effects, license gating, error behavior, and coercion short-circuiting. An output schema exists, so return-value detail is not required. The only completeness gap is the incoherence introduced by the readOnlyHint annotation contradicting the description's explicit read-only scoping.

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 every parameter already documented for requiredness, defaults, and action-specific usage. The description adds general action dispatch and gating behavior, but those are behavioral, not parameter-semantic, details. Coercion of context and rejection of empty eval_action are already present in the schema descriptions, so the description adds little beyond the baseline for fully covered schemas.

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 clearly states the tool is a unified governance entry point that dispatches to one of seven actions by name. It explicitly contrasts with the delimit_gov_* alias siblings, explaining that this is the implementation core while the aliases are thin wrappers. The verb and resource are specific, and the purpose is not a tautology.

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 contains an explicit 'When to use' and 'When NOT to use' section. It names the exact condition for selecting this tool (picking action by name in one call) and directs internal code paths to prefer specific aliases like delimit_gov_health or delimit_gov_evaluate. Sibling contrast is also provided, making routing unambiguous.

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