Skip to main content
Glama
AgentWong

IAC Memory MCP Server

by AgentWong

delete_entity

Remove an entity and its relationships from the Infrastructure-as-Code knowledge graph to maintain accurate IaC documentation.

Instructions

Remove an entity and its relationships from the knowledge graph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEntity ID

Implementation Reference

  • MCP tool handler for delete_entity that delegates to execute_delete_entity and handles errors.
    async def handle_delete_entity(db: Any, arguments: Dict[str, Any], operation_id: str) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
        """Handle delete_entity tool."""
        try:
            logger.info(
                "Deleting entity",
                extra={
                    "entity_id": arguments.get("entity_id"),
                    "operation_id": operation_id,
                },
            )
    
            # Execute deletion
            return execute_delete_entity(db, arguments)
    
        except Exception as e:
            error_msg = f"Failed to delete entity: {str(e)}"
            logger.error(error_msg, extra={"operation_id": operation_id})
            raise McpError(
                types.ErrorData(
                    code=types.INTERNAL_ERROR,
                    message=error_msg,
                    data={
                        "tool": "delete_entity",
                        "operation_id": operation_id,
                    },
                )
            )
  • JSON schema definition for the delete_entity tool parameters.
    "delete_entity": {
        "type": "object",
        "description": "Remove an entity and its relationships from the knowledge graph",
        "required": ["id"],
        "properties": {"id": {"type": "string", "description": "Entity ID"}},
    },
  • Registration of the delete_entity handler in the entity_tool_handlers dictionary, which is merged into the global tool_handlers.
    entity_tool_handlers = {
        "create_entity": handle_create_entity,
        "update_entity": handle_update_entity,
        "delete_entity": handle_delete_entity,
        "view_relationships": handle_view_relationships,
    }
  • Intermediate helper that calls the core delete_entity function and returns MCP TextContent response.
    def execute_delete_entity(
        db: DatabaseManager, arguments: Dict[str, Any]
    ) -> List[TextContent]:
        """Execute delete entity operation."""
        logger.info("Deleting entity", extra={"args": arguments})
    
        success = delete_entity(db, arguments["id"])
        if not success:
            raise DatabaseError(f"Entity not found: {arguments['id']}")
    
        return [TextContent(type="text", text=f"Deleted entity {arguments['id']}")]
  • Core database deletion function that removes observations and the entity from the SQLite database.
    def delete_entity(db: DatabaseManager, entity_id: str) -> bool:
        """Delete an entity and its related observations."""
        try:
            with db.get_connection() as conn:
                conn.execute("BEGIN TRANSACTION")
                conn.execute("DELETE FROM observations WHERE entity_id = ?", (entity_id,))
                cursor = conn.execute("DELETE FROM entities WHERE id = ?", (entity_id,))
                affected = cursor.rowcount > 0
                conn.commit()
                return affected
        except sqlite3.Error as e:
            raise DatabaseError(f"Delete failed: {str(e)}")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Remove' implies a destructive operation, it doesn't specify whether this is irreversible, what permissions are required, how relationships are handled, or what happens on success/failure. For a destructive tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized for a single-parameter tool and front-loads the essential information.

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 insufficient. It doesn't explain what 'remove' entails operationally, what happens to related data, what confirmation might be needed, or what the tool returns. Given the complexity of entity deletion in a knowledge graph, more context is needed.

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%, so the schema already documents the single 'id' parameter. The description doesn't add any additional meaning about the parameter beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Remove') and target ('entity and its relationships from the knowledge graph'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'update_entity' or 'create_entity' beyond the obvious difference in operation type.

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 'update_entity' or 'view_relationships', nor does it mention any prerequisites, constraints, or conditions for usage. It simply states what the tool does without contextual guidance.

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/AgentWong/iac-memory-mcp-server'

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