Skip to main content
Glama
Sign In
UltraProbe

UltraProbe

by ppcvote
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

misp_get_event

Fetch a MISP event by ID and return its attributes (IOCs), with automatic scanning for prompt-injection threats.

Instructions

Fetch a single MISP event by id, including its attributes (IOCs). The response is scanned for prompt-injection payloads before being returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "misp_get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMISP event id (numeric or UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the response is scanned for prompt-injection payloads, but does not mention read-only nature, error handling, or rate limits.

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 concise with two sentences: one for purpose and one for a behavioral detail. No wasted words.

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 includes the inclusion of attributes and the scanning behavior, which is sufficient for a simple fetch tool. No output schema, but the description gives enough context for expected response content.

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?

The schema covers the id parameter with a description, and the description does not add additional meaning beyond what is in the schema. Baseline score for high schema coverage.

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 that the tool fetches a single MISP event by id, including its attributes. This distinguishes it from sibling tools like misp_list_events and misp_search_events.

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 does not explicitly state when to use this tool versus alternatives, but the purpose of fetching a single event by ID is implicit. No exclusions or guidance is provided.

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