tie-mcp-server

get_event

Retrieve a specific event instance from Tenable Identity Exposure by its ID and directory ID.

Instructions

Get event instance by id.

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": {
      "directoryId": "<directoryId>",
      "id": "<id>"
    },
    "name": "get_event"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Path parameter: id
`directoryId`	Yes	Path parameter: directoryId

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 6, 2026

TDQS

B3.2/5.0

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 states a read operation ('Get') but does not confirm read-only behavior, required permissions, or potential side effects. The description is insufficient for a tool with no annotation safety net.

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 only four words, front-loaded with the key action and resource. Every word is necessary, achieving maximum conciseness without loss of clarity.

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?

Given the tool's simplicity (2 required params, no output schema, no nested objects), the description is largely complete. It could mention the return type or expected output, but the absence is minor given the straightforward retrieval purpose.

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 as 'Path parameter: id' and 'Path parameter: directoryId', but these descriptions are minimal. The tool description adds no extra meaning, so it meets the baseline for high schema coverage without enhancing parameter understanding.

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 'Get' and the resource 'event instance by id', which distinguishes it from siblings like 'get_event_by_directory' that retrieve events by different criteria. However, it does not explicitly mention the required parameters (directoryId, id) beyond what the name implies.

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 like 'get_event_by_directory' or other getters. The description solely states the function without contextual usage advice.

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

Deploy Server