tie-mcp-server

get_ad_object_by_checker

Retrieve an Active Directory object with security deviances by providing the profile ID and checker ID.

Instructions

Retrieve an AD object by id that have deviances for a specific profile and checker Note: profileId selects a configuration profile (a lens, not a container). If the user has not specified a profile, call get_preferred_profile (or get_preferences) and use preferredProfileId — do not assume profile 1.

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": {
      "profileId": "<profileId>",
      "checkerId": "<checkerId>",
      "id": "<id>"
    },
    "name": "get_ad_object_by_checker"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Path parameter: id
`checkerId`	Yes	Path parameter: checkerId
`profileId`	Yes	Path parameter: profileId
`showIgnored`	No	Query parameter: showIgnored

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 6, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds behavioral context by noting that the object must have deviances and that profileId is a lens, not a container. However, it does not disclose permissions, read-only nature, or response structure.

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 sentence plus a note, with no wasted words. The note is well-positioned and essential for correct usage.

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

Completeness3/5

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

There is no output schema, and the description does not describe the return structure or error cases. While the prerequisite note is helpful, the agent lacks information about the returned object's fields, pagination, or error handling.

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

Parameters4/5

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

Schema coverage is 100% with minimal descriptions. The description adds significant meaning for profileId by explaining it selects a configuration profile (lens) and providing a prerequisite step. Other parameters (id, checkerId, showIgnored) are not elaborated beyond schema.

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 tool retrieves an AD object by id that has deviances for a specific profile and checker, using a specific verb and resource. It distinguishes from sibling tools like get_ad_object_by_directory and get_ad_object_in_event by focusing on checker and profile.

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?

The description provides clear guidance on how to determine the correct profileId, instructing to call get_preferred_profile or get_preferences if not specified, and warns against assuming profile 1. However, it does not explicitly compare to other get_ad_object_* tools or state when not to use it.

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

Deploy Server