tie-mcp-server

get_ad_object_in_event

Retrieve a specific Active Directory object linked to a security event using its event ID and object ID.

Instructions

Get one ad-object by event and 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": {
      "infrastructureId": "<infrastructureId>",
      "directoryId": "<directoryId>",
      "eventId": "<eventId>",
      "id": "<id>"
    },
    "name": "get_ad_object_in_event"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Path parameter: id
`eventId`	Yes	Path parameter: eventId
`directoryId`	Yes	Path parameter: directoryId
`infrastructureId`	Yes	Path parameter: infrastructureId

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It only states it 'gets' an object, but does not disclose permissions, rate limits, or behavior on missing objects. Minimal transparency.

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

Conciseness3/5

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

The description is a single short sentence, which is concise, but it lacks necessary detail. It is under-specified rather than efficiently informative.

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?

No output schema and no description of return values. Parameters have poor descriptions. The description does not adequately prepare an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions are uninformative ('Path parameter: id'). The tool description merely restates 'by event and by id' without adding meaning. No added value beyond schema default.

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 'Get one ad-object by event and by id' clearly states the verb (Get), resource (ad-object), and criteria (event and id). It distinguishes from sibling tools like get_ad_object_by_checker or get_ad_object_by_directory.

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 on when to use this tool versus alternatives. There are many sibling tools (e.g., get_ad_object_by_checker, search_ad_objects) but the description does not provide any context for selection.

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

Deploy Server