tie-mcp-server

update_deviances_by_checker

Update deviance instances for a given checker by applying a profile's configuration. Automatically uses the user's preferred profile if none specified.

Instructions

Update instances matching a checkerId. 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>",
      "body": "<body>"
    },
    "name": "update_deviances_by_checker"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Validates the POST /checker/:checkerId/deviances request
`checkerId`	Yes	Query parameter: checkerId
`profileId`	Yes	Query parameter: profileId

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided. Description discloses that profileId is a lens, not a container, but does not reveal behavioral traits like destructiveness, permission requirements, or idempotency. For a mutation tool, this is insufficient.

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

Conciseness4/5

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

Two sentences, front-loaded with purpose. Second sentence adds necessary context. No wasted words.

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?

Covers purpose and profileId nuance. Lacks explanation of body content beyond ignoreUntil, no mention of bulk update behavior, and no output schema details. Adequate but incomplete.

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%, baseline 3. Description adds meaning for profileId (lens, not container; workflow hint) but adds no extra semantics for checkerId or body beyond schema descriptions.

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 states 'Update instances matching a checkerId', which is a specific verb and resource. It distinguishes from siblings like update_deviance and update_deviances_by_ad_object. However, it could be more explicit about updating deviances.

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?

Provides clear guidance on profileId semantics and a workflow hint to call get_preferred_profile if profile not specified. Does not explicitly compare to alternative tools or state when not to use.

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

Deploy Server