Auto_DeleteAutoImport
Deletes an auto-import configuration to stop scheduled data imports in BeezUP store management.
Instructions
Delete Auto Import
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Deletes an auto-import configuration to stop scheduled data imports in BeezUP store management.
Delete Auto Import
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. The word 'Delete' implies a destructive action, but it does not explain any side effects, required permissions, or what happens to related data. Minimal disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, consisting of a single phrase that efficiently communicates the tool's purpose. It wastes no words and is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations, output schema, and parameters, the description should provide more context about the tool's behavior, return value, or preconditions. It is insufficiently complete for an AI agent to use confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters, so schema coverage is 100%. With zero parameters, the baseline is 4, and the description adds no further parameter info, which is acceptable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete Auto Import' clearly states the action and resource, matching the tool name. It is a specific verb and resource, but does not differentiate from sibling tools like Auto_PauseAutoImport or Auto_ResumeAutoImport.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 alternatives such as Auto_PauseAutoImport or Auto_ConfigureAutoImportInterval. It lacks any usage context or preconditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ktmcp-cli/beezup'
If you have feedback or need assistance with the MCP directory API, please join our Discord server