Skip to main content
Glama

misp_delete_attribute

Delete an attribute from MISP, choosing between a soft delete or a permanent hard delete. Provide the attribute ID to remove the indicator from the platform.

Instructions

Delete (soft or hard) an attribute from MISP

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attributeIdYesAttribute ID to delete
hardNoHard delete (permanent) instead of soft delete

Implementation Reference

  • Registration of 'misp_delete_attribute' tool with server.tool(), defining the schema (attributeId: string, hard: optional boolean) and the handler callback.
    server.tool(
      "misp_delete_attribute",
      "Delete (soft or hard) an attribute from MISP",
      {
        attributeId: z.string().describe("Attribute ID to delete"),
        hard: z.boolean().optional().describe("Hard delete (permanent) instead of soft delete"),
      },
      async ({ attributeId, hard }) => {
        try {
          const result = await client.deleteAttribute(attributeId, hard);
          return {
            content: [
              { type: "text", text: result.message || `Attribute ${attributeId} deleted successfully.` },
            ],
          };
        } catch (err) {
          return {
            content: [
              { type: "text", text: `Error deleting attribute: ${err instanceof Error ? err.message : String(err)}` },
            ],
            isError: true,
          };
        }
      }
    );
  • Handler function that receives { attributeId, hard }, calls client.deleteAttribute(), and returns success/error content.
    async ({ attributeId, hard }) => {
      try {
        const result = await client.deleteAttribute(attributeId, hard);
        return {
          content: [
            { type: "text", text: result.message || `Attribute ${attributeId} deleted successfully.` },
          ],
        };
      } catch (err) {
        return {
          content: [
            { type: "text", text: `Error deleting attribute: ${err instanceof Error ? err.message : String(err)}` },
          ],
          isError: true,
        };
      }
    }
  • Input schema definition for the tool: attributeId (required string) and hard (optional boolean for permanent delete).
    {
      attributeId: z.string().describe("Attribute ID to delete"),
      hard: z.boolean().optional().describe("Hard delete (permanent) instead of soft delete"),
    },
  • Client-side implementation of deleteAttribute. Sends POST request to /attributes/delete/{id} with optional { hard: 1 } body for permanent deletion.
    async deleteAttribute(
      attributeId: string,
      hard = false
    ): Promise<{ message: string }> {
      const body = hard ? { hard: 1 } : {};
      return this.request<{ message: string }>(
        "POST",
        `/attributes/delete/${encodeId(attributeId, "attributeId")}`,
        body
      );
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions soft and hard delete but does not explain what soft delete entails (e.g., reversibility) or any destructive implications. No details on permissions, side effects, or return behavior are included.

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, concise sentence that communicates the core functionality without any extraneous words. It achieves maximum 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?

With no output schema, the description does not indicate what the tool returns (e.g., success message, status). It also lacks information about error conditions or default behavior for the 'hard' parameter. The tool is simple, but critical context is missing.

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 coverage is 100%, with both parameters described in the schema. The description adds the context of 'soft or hard' which aligns with the 'hard' parameter but does not provide significant additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Delete (soft or hard) an attribute from MISP', using a specific verb ('Delete') and resource ('attribute'). It distinguishes from siblings like misp_delete_event and misp_delete_object by specifying the attribute resource.

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 does not provide any guidance on when to use soft vs hard delete, nor does it mention scenarios where this tool should not be used or suggest alternatives. No prerequisites or context are given.

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/solomonneas/misp-mcp'

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