Skip to main content
Glama

misp_delete_event

Delete a MISP event by providing its event ID. Requires appropriate permissions.

Instructions

Delete a MISP event (requires appropriate permissions)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYesEvent ID to delete

Implementation Reference

  • The tool handler for 'misp_delete_event'. Registers an MCP tool that accepts an eventId string parameter, calls client.deleteEvent(eventId), and returns the result message or an error.
    // Delete event
    server.tool(
      "misp_delete_event",
      "Delete a MISP event (requires appropriate permissions)",
      {
        eventId: z.string().describe("Event ID to delete"),
      },
      async ({ eventId }) => {
        try {
          const result = await client.deleteEvent(eventId);
          return {
            content: [
              {
                type: "text",
                text: result.message || `Event ${eventId} deleted.`,
              },
            ],
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: `Error deleting event: ${err instanceof Error ? err.message : String(err)}`,
              },
            ],
            isError: true,
          };
        }
      }
  • Registration of the 'misp_delete_event' tool via server.tool() inside the registerServerTools function, which is called from src/index.ts line 42.
    server.tool(
      "misp_delete_event",
      "Delete a MISP event (requires appropriate permissions)",
      {
        eventId: z.string().describe("Event ID to delete"),
      },
      async ({ eventId }) => {
        try {
          const result = await client.deleteEvent(eventId);
          return {
            content: [
              {
                type: "text",
                text: result.message || `Event ${eventId} deleted.`,
              },
            ],
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: `Error deleting event: ${err instanceof Error ? err.message : String(err)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Zod schema for the 'misp_delete_event' tool: expects a single required string parameter 'eventId'.
    {
      eventId: z.string().describe("Event ID to delete"),
    },
  • The MispClient.deleteEvent method - sends a POST request to /events/delete/{eventId} on the MISP API and returns a message.
    async deleteEvent(eventId: string): Promise<{ message: string }> {
      return this.request<{ message: string }>(
        "POST",
        `/events/delete/${encodeId(eventId, "eventId")}`
      );
    }
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions permissions, but does not describe whether deletion is irreversible, cascading, or what happens to associated data. This is minimal disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two sentences) and front-loaded with the core action. It is efficient, though the permission note could be integrated more seamlessly. Still, every sentence earns its place.

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 delete operation with many sibling tools, the description lacks completeness. It does not explain prerequisites, effects (e.g., irreversible), error handling, or return values. The lack of output schema makes this omission more significant.

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 a clear description for the single parameter 'eventId'. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 verb ('Delete'), the resource ('a MISP event'), and hints at a prerequisite ('requires appropriate permissions'). It distinguishes from sibling tools like misp_delete_attribute and misp_delete_object by specifying the event 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?

No guidance is provided on when to use this tool versus alternatives (e.g., misp_delete_attribute, misp_delete_object) or when not to use it. The description lacks context for decision-making.

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