Skip to main content
Glama

misp_get_event

Retrieve all details of a MISP event, including attributes, objects, tags, and related events.

Instructions

Get full details of a specific MISP event including all attributes, objects, tags, and related events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYesEvent ID to retrieve

Implementation Reference

  • The MCP tool handler for 'misp_get_event'. Calls client.getEvent(eventId) and formats the response into structured JSON with event details, attributes, objects, galaxies, and related events.
    // Get event details
    server.tool(
      "misp_get_event",
      "Get full details of a specific MISP event including all attributes, objects, tags, and related events",
      {
        eventId: z.string().describe("Event ID to retrieve"),
      },
      async ({ eventId }) => {
        try {
          const event = await client.getEvent(eventId);
    
          const result = {
            id: event.id,
            uuid: event.uuid,
            info: event.info,
            date: event.date,
            threat_level: ["", "High", "Medium", "Low", "Undefined"][
              parseInt(event.threat_level_id) || 0
            ],
            analysis: ["Initial", "Ongoing", "Complete"][parseInt(event.analysis) || 0],
            distribution: ["Organization", "Community", "Connected communities", "All communities", "Sharing group"][
              parseInt(event.distribution) || 0
            ],
            published: event.published,
            org: event.Orgc?.name || "Unknown",
            tags: (event.Tag || []).map((t) => t.name),
            attribute_count: event.attribute_count,
            attributes: (event.Attribute || []).map((a) => ({
              id: a.id,
              type: a.type,
              category: a.category,
              value: a.value,
              to_ids: a.to_ids,
              comment: a.comment,
            })),
            objects: (event.Object || []).map((o) => ({
              id: o.id,
              name: o.name,
              meta_category: o.meta_category,
              attributes: (o.Attribute || []).map((a) => ({
                type: a.type,
                value: a.value,
              })),
            })),
            galaxies: (event.Galaxy || []).map((g) => ({
              name: g.name,
              type: g.type,
              clusters: (g.GalaxyCluster || []).map((c) => c.value),
            })),
            related_events: (event.RelatedEvent || []).map((r) => ({
              id: r.Event.id,
              info: r.Event.info,
              date: r.Event.date,
            })),
          };
    
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
          };
        } catch (err) {
          return {
            content: [
              { type: "text", text: `Error getting event: ${err instanceof Error ? err.message : String(err)}` },
            ],
            isError: true,
          };
        }
      }
    );
  • Zod schema definition for the 'misp_get_event' tool: accepts a required 'eventId' (string).
    "Get full details of a specific MISP event including all attributes, objects, tags, and related events",
    {
      eventId: z.string().describe("Event ID to retrieve"),
    },
  • The 'registerEventTools' function registers all event-related tools, including 'misp_get_event', on the MCP server.
    import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
    import { z } from "zod";
    import type { MispClient } from "../client.js";
    
    export function registerEventTools(server: McpServer, client: MispClient): void {
  • src/index.ts:30-31 (registration)
    Registration call in the main index.ts: registerEventTools(server, client) which wires up the tool on the MCP server.
    // Register all tools
    registerEventTools(server, client);
  • Client-side helper method 'getEvent' that performs the HTTP GET to /events/view/{eventId} and returns the MispEvent data.
    async getEvent(eventId: string): Promise<MispEvent> {
      const data = await this.request<EventResponse>(
        "GET",
        `/events/view/${encodeId(eventId, "eventId")}`
      );
      return data.Event;
    }
Behavior2/5

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

With no annotations provided, the description must convey behavioral traits. It only describes the output ('full details') but does not state that the operation is read-only, whether authentication is required, rate limits, or potential response size. This is a 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.

Conciseness5/5

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

The description is a single 15-word sentence, front-loaded with verb and resource, and contains no redundant information. Highly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the key output components and is sufficient for a simple retrieval tool with one parameter. However, it could mention the return structure or error conditions since no output schema exists.

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 the parameter eventId described as 'Event ID to retrieve'. The description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

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 the verb 'Get', the resource 'full details of a specific MISP event', and enumerates included components (attributes, objects, tags, related events). It effectively distinguishes from sibling tools like misp_search_events and misp_create_event.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a specific event ID, but does not explicitly state when to use this tool over alternatives like misp_search_events or misp_get_related_events. No exclusions or prerequisites are mentioned.

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