Skip to main content
Glama

zentao_delete_program

Delete a program from Zentao by providing its ID to remove the project set from the system.

Instructions

删除禅道项目集

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes项目集 ID
Behavior2/5

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

The description only states the action (delete) without any behavioral details. Since no annotations are provided, the description should disclose consequences, such as whether the program deletion is irreversible, affects related data, or requires special permissions. This omission reduces transparency.

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 extremely concise (one short phrase) but lacks structure. While brevity is valued, it does not fully compensate for missing context. The front-loading is adequate but the content is too sparse to be highly effective.

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 tool's simplicity (one parameter, no output schema) and the presence of many sibling tools, the description is insufficient. It does not explain what a 'program' is in ZenTao context or how deletion impacts other entities. The lack of completeness makes it harder for an agent to use correctly without external knowledge.

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 schema has 100% coverage with one parameter 'id' described as '项目集 ID'. The description adds no extra meaning beyond this, so the baseline of 3 applies. No further elaboration on ID format or source is provided.

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

Purpose4/5

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

The description '删除禅道项目集' clearly indicates the tool deletes a ZenTao program. While it is a direct restatement of the name, it adds the product context '禅道', making the purpose unambiguous and distinguishing it from general delete operations.

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 tool versus sibling tools like zentao_delete_project, zentao_delete_product, or zentao_delete_feedback. The lack of usage context or prerequisites limits its helpfulness for an AI agent deciding between similar tools.

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/HouEngineer/sdw-zentao-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server