Skip to main content
Glama
lidless-labs

misp-mcp

by lidless-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

misp_create_event

Create a MISP event to document incidents or threat intelligence without publishing. Specify details like description, distribution, threat level, and analysis phase.

Instructions

Create a new MISP event for documenting incidents or threat intelligence. Does not publish - use misp_publish_event separately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoEvent date (YYYY-MM-DD)
infoYesEvent description/title
tagsNoTags to apply
analysisYes0=Initial, 1=Ongoing, 2=Complete
threatLevelYes1=High, 2=Medium, 3=Low, 4=Undefined
distributionYes0=Organization only, 1=Community, 2=Connected communities, 3=All communities, 4=Sharing group

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed11 schema fields changedv1.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / analysis / anyOf
      Added value: +[
+  {
+    "const": 0,
+    "type": "number"
+  },
+  {
+    "const": 1,
+    "type": "number"
+  },
+  {
+    "const": 2,
+    "type": "number"
+  }
+]
    • removedInput schema / properties / analysis / enum
      Removed value: -[
-  0,
-  1,
-  2
-]
    • removedInput schema / properties / analysis / type
      Removed value: -"number"
    • addedInput schema / properties / distribution / anyOf
      Added value: +[
+  {
+    "const": 0,
+    "type": "number"
+  },
+  {
+    "const": 1,
+    "type": "number"
+  },
+  {
+    "const": 2,
+    "type": "number"
+  },
+  {
+    "const": 3,
+    "type": "number"
+  },
+  {
+    "const": 4,
+    "type": "number"
+  }
+]
    • removedInput schema / properties / distribution / enum
      Removed value: -[
-  0,
-  1,
-  2,
-  3,
-  4
-]
    • removedInput schema / properties / distribution / type
      Removed value: -"number"
    • removedInput schema / properties / published
      Removed value: -{
-  "description": "Publish immediately",
-  "type": "boolean"
-}
    • addedInput schema / properties / threatLevel / anyOf
      Added value: +[
+  {
+    "const": 1,
+    "type": "number"
+  },
+  {
+    "const": 2,
+    "type": "number"
+  },
+  {
+    "const": 3,
+    "type": "number"
+  },
+  {
+    "const": 4,
+    "type": "number"
+  }
+]
    • removedInput schema / properties / threatLevel / enum
      Removed value: -[
-  1,
-  2,
-  3,
-  4
-]
    • removedInput schema / properties / threatLevel / type
      Removed value: -"number"
  3. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided. Description notes it does not publish but does not disclose other behaviors like whether the event is created in draft mode, permission requirements, or side effects. More detail expected given no annotations.

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?

Two concise sentences with no redundancy. Critical information is front-loaded efficiently.

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?

Adequately covers purpose and key behavior (no publish). Missing explanation of return value or output format, which would be helpful since no output schema is provided.

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 baseline is 3. The description repeats the schema's parameter details without adding new meaning or usage context.

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?

Clearly states the tool's purpose: 'Create a new MISP event for documenting incidents or threat intelligence.' Distinguishes from sibling by noting it does not publish, guiding to misp_publish_event.

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

Usage Guidelines4/5

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

Explicitly directs to use misp_publish_event separately for publishing. Lacks broader context on when to use this versus other creation tools like misp_add_attribute, but provides clear immediate guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools