Skip to main content
Glama
snilld-ai

OpenAI Assistant MCP Server

by snilld-ai

delete-file

Remove files from the OpenAI Assistant environment to manage storage and maintain organized workspaces by specifying file IDs.

Instructions

Delete a file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idYesThe ID of the file to delete

Implementation Reference

  • Implements the core logic for deleting a file using the OpenAI Files API.
    async def delete_file(self, file_id: str):
        try:
            response = await self.client.files.delete(file_id)
            return response
        except Exception as e:
            logger.error(f"Failed to delete file {file_id}: {str(e)}")
            raise
  • Registers the 'delete-file' tool with its name, description, and input schema in the list_tools callback.
    types.Tool(
        name="delete-file",
        description="Delete a file",
        inputSchema={
            "type": "object",
            "properties": {
                "file_id": {"type": "string", "description": "The ID of the file to delete"}
            },
            "required": ["file_id"]
        }
    )
  • Handles the tool call dispatch for 'delete-file' by extracting arguments and calling the LLMConnector's delete_file method.
    elif name == "delete-file":
        file_id = arguments["file_id"]
        response = await connector.delete_file(file_id)
        return [types.TextContent(type="text", text=f"File deleted: {response.id}, status: {'deleted' if response.deleted else 'not deleted'}")]
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete a file' implies a destructive, irreversible mutation, but the description doesn't warn about this, mention permissions required, or describe what happens upon success/failure. This is inadequate 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 extremely concise with just three words, front-loading the key action and resource. There's zero waste or redundancy, making it efficient for quick comprehension.

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 tool with no annotations and no output schema, the description is incomplete. It lacks critical context like behavioral warnings, success/error outcomes, or usage constraints, leaving significant gaps for an agent to operate safely and effectively.

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 schema fully documenting the single parameter 'file_id'. The description adds no parameter details beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without adding value.

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 resource ('a file'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete-assistant' or 'list-files' beyond the resource name, which prevents a perfect score.

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 versus alternatives like 'list-files' or 'upload-file', nor does it mention prerequisites (e.g., needing a valid file_id). It's a bare statement with no contextual usage information.

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