Skip to main content
Glama
snilld-ai

OpenAI Assistant MCP Server

by snilld-ai

delete-assistant

Remove an OpenAI assistant by providing its ID to manage your assistant inventory and maintain organization.

Instructions

Delete an OpenAI assistant

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assistant_idYesThe ID of the assistant to delete

Implementation Reference

  • The core handler function in LLMConnector that deletes the OpenAI assistant using the AsyncOpenAI client.
    async def delete_assistant(self, assistant_id: str):
        try:
            response = await self.client.beta.assistants.delete(assistant_id)
            return response
        except Exception as e:
            logger.error(f"Failed to delete assistant {assistant_id}: {str(e)}")
            raise
  • Registers the 'delete-assistant' tool in the list_tools handler, including its description and input schema.
    types.Tool(
        name="delete-assistant",
        description="Delete an OpenAI assistant",
        inputSchema={
            "type": "object",
            "properties": {
                "assistant_id": {"type": "string", "description": "The ID of the assistant to delete"}
            },
            "required": ["assistant_id"]
        }
    ),
  • Dispatches the tool call to the LLMConnector's delete_assistant method and formats the response.
    elif name == "delete-assistant":
        assistant_id = arguments["assistant_id"]
        response = await connector.delete_assistant(assistant_id)
        return [types.TextContent(type="text", text=f"Assistant deleted: {response.id}, status: {'deleted' if response.deleted else 'not deleted'}")]
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool deletes an assistant, implying a destructive mutation, but lacks details on permissions required, whether deletion is permanent or reversible, rate limits, or what happens to associated data. This is a significant gap for a destructive tool.

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, efficient sentence with zero waste. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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?

For a destructive mutation tool with no annotations and no output schema, the description is inadequate. It lacks critical behavioral context (e.g., permanence, side effects) and doesn't compensate for the absence of structured fields, leaving the agent with insufficient information for safe invocation.

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?

Schema description coverage is 100%, with the single parameter 'assistant_id' documented in the schema. The description doesn't add any parameter details beyond what the schema provides, such as format examples or sourcing guidance. Baseline 3 is appropriate as the schema handles the parameter documentation.

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 states the action ('Delete') and target resource ('an OpenAI assistant'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like 'delete-file' beyond the resource type, missing explicit sibling distinction.

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 alternatives. The description doesn't mention prerequisites (e.g., needing an existing assistant ID), exclusions, or comparisons with sibling tools like 'update-assistant' or 'retrieve-assistant' for different operations.

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/snilld-ai/openai-assistant-mcp'

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