Skip to main content
Glama

_delimit_gov_impl

Perform governance operations including health checks, policy evaluation, task creation, running, and verification for repositories.

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 provided, and the description does not disclose side effects, permission requirements, or whether actions are destructive (e.g., 'run' might modify state). For a tool with multiple sub-operations, this is insufficient.

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?

Description is very short but not front-loaded: the first sentence is ambiguous ('Pro for...'). It is concise but lacks clarity and structure, missing critical context.

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, many sibling tools), the description is incomplete. It does not explain when to use this vs. individual gov tools, nor does it describe output or behavior for each action. Output schema exists but description ignores it.

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?

Input schema has 100% coverage with descriptions for all 8 parameters, so the schema already documents parameters well. The description only lists action names without adding semantic meaning beyond what the schema provides.

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?

Description states 'Manage governance' and lists actions, giving a general idea but failing to clarify that this is an underlying implementation tool vs. separate sibling tools like delimit_gov_health. The purpose is vaguely clear but not distinct from similar tools.

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 on when to use this tool versus the many sibling tools that perform specific governance actions (e.g., delimit_gov_evaluate). Agent cannot determine if this is for batch operations or internal use.

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