Skip to main content
Glama
shivanshu814

DreamingAI MCP Server

by shivanshu814

delete_agent

Delete an AI agent from DreamingAI with its unique agent ID, removing unused agents from your environment.

Instructions

Delete an AI agent from DreamingAI

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdYesID of the agent to delete
Behavior2/5

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

With no annotations, the description must disclose behavioral traits on its own. It only states 'Delete an AI agent' without mentioning irreversibility, potential cascading deletion of associated data, or whether the operation requires confirmation. This is a significant gap for a destructive operation.

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

Conciseness5/5

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

The description is a single, concise sentence that directly states the action. It is front-loaded with the verb and object, and every word contributes to the meaning. This is an example of efficient structure.

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

Completeness3/5

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

For a simple delete operation, the description is minimal but omits critical context such as permanence, consequences, and return values. Although the schema covers the parameter, the lack of annotations and output schema means the description should provide more behavioral context than it does.

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 already fully describes the single parameter agentId as 'ID of the agent to delete', and the tool description adds no extra semantic information about the parameter. Since schema coverage is 100%, the baseline score of 3 applies, and the description does not elevate it.

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's purpose: deleting an AI agent. It uses a specific verb 'Delete' and a specific resource 'AI agent', which distinguishes it from sibling tools like get_agent, create_agent, or update_agent. The addition of 'from DreamingAI' provides product context.

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?

The description provides no guidance on when to use this tool relative to alternatives. It does not mention any prerequisites, exclusions, or scenarios where this is the appropriate choice. No direction is given regarding checking for existing agents or considering destructive effects.

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/shivanshu814/dreamingai-mcp-server'

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