Skip to main content
Glama

_delimit_gov_impl

Execute governance actions including health, status, policy evaluation, task creation, execution, and verification for compliance management.

Instructions

Manage governance (Pro for policy/evaluate/new_task/run/verify).

Actions: health, status, policy, evaluate, new_task, run, verify.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoWhich governance operation to perform.health
repoNoRepository path..
eval_actionNoThe action to evaluate (for action='evaluate').
contextNoAdditional context (for action='evaluate').
titleNoTask title (for action='new_task').
scopeNoTask scope (for action='new_task').
risk_levelNoRisk level low/medium/high/critical (for action='new_task').medium
task_idNoTask ID (for action='run' or action='verify').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must bear full burden. It does not describe the behavior of each action (e.g., what health, status, policy do) or the dispatching mechanism. The description is insufficient for an agent to understand the tool's effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is short (two sentences) but the first sentence is unclear ('Pro for policy/...'). The second sentence redundantly lists actions already defined by the parameter. It is concise but not well-structured or clear.

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

Completeness2/5

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

Given the complexity (8 parameters, multiple actions, and an output schema), the description is incomplete. It fails to explain behavior per action, usage patterns, or the output, leaving the agent underinformed.

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?

The input schema has 100% coverage with descriptions for all 8 parameters. The description adds no extra parameter information beyond what the schema already provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Manage governance' and lists actions, but it does not clearly differentiate this combined tool from the individual sibling tools like delimit_gov_evaluate or delimit_gov_health. The purpose is implied but vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this combined tool versus the individual governance action tools. There is no mention of usage context or alternatives.

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