tie-mcp-server

list_deviances_by_event

Retrieves all deviances for a given event, using profile, infrastructure, and directory identifiers to filter results.

Instructions

Get all deviances by eventId. 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>",
      "infrastructureId": "<infrastructureId>",
      "directoryId": "<directoryId>",
      "eventId": "<eventId>",
      "body": "<body>"
    },
    "name": "list_deviances_by_event"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Validates POST /profiles/:profileId/infrastructures/:infrastructureId/directories/:directoryId/events/:eventId/deviances request payload
`page`	No	Query parameter: page
`eventId`	Yes	Path parameter: eventId
`perPage`	No	Query parameter: perPage
`profileId`	Yes	Path parameter: profileId
`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

A4/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 mentions that profileId is a lens, but lacks details on return format, error handling, pagination behavior, or side effects. This is insufficient for a tool with 7 parameters and nested objects.

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 two sentences: one for core purpose and one for critical usage note. It is front-loaded with the action and resource, and the additional guidance is clearly separated. No unnecessary words.

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?

The tool has 7 parameters (including a nested body with arrays), no output schema, and no annotations. The description does not explain the body parameter, pagination parameters (page, perPage), or what the returned deviances represent. This leaves significant gaps for an agent to use the tool correctly.

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%, so baseline is 3. The description adds value by explaining that profileId 'selects a configuration profile (a lens, not a container)' and provides usage guidance. This goes beyond the schema descriptions of the parameters.

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's purpose: 'Get all deviances by eventId'. It uses a specific verb and clarifies that profileId is a lens, distinguishing it from sibling tools like list_deviances_by_checker and list_deviances_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 Guidelines5/5

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

The description provides explicit guidance on determining profileId: if unspecified, call get_preferred_profile or get_preferences and use preferredProfileId, with the warning not to assume profile 1. This clearly informs when to use the tool and prerequisites.

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

Deploy Server