Skip to main content
Glama

delete_metadata

Remove specific metadata from nodes in the MemoryMesh knowledge graph. Input an array of deletions specifying node names and metadata items to clean up data efficiently.

Instructions

Delete specific metadata from nodes in the knowledge graph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deletionsYesArray of metadata deletions

Implementation Reference

  • The core handler logic for the 'delete_metadata' tool, which invokes the underlying deleteMetadata method on the knowledge graph manager and formats the success response.
    case "delete_metadata":
        await this.knowledgeGraphManager.deleteMetadata(args.deletions);
        return formatToolResponse({
            actionTaken: "Deleted metadata from nodes"
        });
  • Defines the tool metadata including name, description, and input schema validation for the deletions parameter.
    {
        name: "delete_metadata",
        description: "Delete specific metadata from nodes in the knowledge graph",
        inputSchema: {
            type: "object",
            properties: {
                deletions: {
                    type: "array",
                    description: "Array of metadata deletions",
                    items: {
                        type: "object",
                        description: "Metadata deletion",
                        properties: {
                            nodeName: {type: "string", description: "The name of the node containing the metadata"},
                            metadata: {
                                type: "array",
                                items: {type: "string", description: "Metadata item to delete"},
                                description: "An array of metadata to delete"
                            },
                        },
                        required: ["nodeName", "metadata"],
                    },
                },
            },
            required: ["deletions"],
        },
    }
  • Registers all static tools (including delete_metadata from staticTools.ts) into the central ToolsRegistry map during initialization.
    // Register static tools
    allStaticTools.forEach(tool => {
        this.tools.set(tool.name, tool);
    });
  • Routes 'delete_metadata' tool calls to the appropriate MetadataToolHandler instance based on regex matching.
    if (toolName.match(/^(add|delete)_metadata$/)) {
        return this.metadataHandler;
Behavior2/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. While 'Delete' implies a destructive mutation, the description doesn't specify whether this operation is reversible, requires specific permissions, has side effects on the graph structure, or provides confirmation of deletion. For a destructive tool with zero annotation coverage, this is inadequate transparency.

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 without any fluff or redundancy. It's front-loaded with the core action and target, making it immediately understandable. Every word earns its place, achieving optimal conciseness.

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?

Given the tool's destructive nature, lack of annotations, and absence of an output schema, the description is incomplete. It doesn't cover behavioral aspects like safety, permissions, or return values, nor does it provide usage context relative to sibling tools. For a mutation tool in a complex graph system, this leaves critical gaps for an AI agent.

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 'deletions' fully documented in the schema as an array of objects with 'nodeName' and 'metadata' fields. The description adds no additional meaning beyond the schema, such as explaining what constitutes valid metadata items or deletion constraints. Baseline 3 is appropriate when the schema does all the work.

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 ('specific metadata from nodes in the knowledge graph'), which is a specific verb+resource combination. It distinguishes itself from sibling tools like 'delete_nodes' or 'delete_edges' by focusing on metadata deletion rather than node/edge deletion. However, it doesn't explicitly contrast with 'add_metadata' or other metadata-related tools, keeping it from 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. It doesn't mention prerequisites (e.g., metadata must exist), exclusions (e.g., cannot delete all metadata at once), or suggest other tools like 'update_metadata' if modification is needed instead. With many sibling tools available, this lack of contextual guidance is a significant gap.

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

Related 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/CheMiguel23/MemoryMesh'

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