Skip to main content
Glama
taylorleese

mcp-toolz

context_delete

Remove specific context entries by ID to manage stored session data and maintain organized workspace resources.

Instructions

Delete a specific context by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
context_idYesContext ID to delete

Implementation Reference

  • Handler in call_tool method that executes the context_delete tool by extracting context_id and calling storage.delete_context, returning success or not found message.
    if name == "context_delete":
        context_id = arguments["context_id"]
        deleted = self.storage.delete_context(context_id)
        if deleted:
            return [TextContent(type="text", text=f"✓ Context {context_id} deleted")]
        return [TextContent(type="text", text=f"Context {context_id} not found")]
  • Tool schema definition including input schema for context_delete in list_tools method.
    Tool(
        name="context_delete",
        description="Delete a specific context by ID",
        inputSchema={
            "type": "object",
            "properties": {
                "context_id": {"type": "string", "description": "Context ID to delete"},
            },
            "required": ["context_id"],
        },
    ),
  • Core helper method in ContextStorage that performs the actual database deletion of the context by ID.
    def delete_context(self, context_id: str) -> bool:
        """Delete a context by ID. Returns True if deleted, False if not found."""
        with closing(sqlite3.connect(self.db_path)) as conn:
            cursor = conn.execute("DELETE FROM contexts WHERE id = ?", (context_id,))
            conn.commit()
            return cursor.rowcount > 0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if deletion is permanent, requires specific permissions, has side effects (e.g., affecting related data), or error handling, which 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 a single, direct sentence with zero wasted words, front-loading the key action and resource. It efficiently communicates the core purpose without unnecessary elaboration, making it easy for an agent 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 tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as what 'delete' entails (e.g., irreversible), expected outcomes, error scenarios, or how it differs from other deletion tools, leaving significant gaps for safe and effective use.

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 description adds minimal meaning beyond the input schema, which has 100% coverage and clearly documents the 'context_id' parameter. The description implies the ID must be specific but doesn't provide additional context like format examples or validation rules, meeting the baseline for high schema coverage.

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 specific context by ID'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'todo_delete' or 'context_get', which would require specifying what distinguishes context deletion from other deletion or context 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing context ID), exclusions, or comparisons to siblings like 'context_list' or 'todo_delete', leaving the agent to infer usage context independently.

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/taylorleese/mcp-toolz'

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