ucontrol-mcp

Ucontrol Read Schema Ire Rules

ucontrol_read_schema_ire_rules

Read-onlyIdempotent

Retrieve Identification/Reconciliation Engine rules for a specified asset kind to understand matching and reconciliation logic.

Instructions

Schema API: read Identification/Reconciliation Engine rules for an asset kind.

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": {
      "kind": "<kind>"
    },
    "name": "ucontrol_read_schema_ire_rules"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes	Asset kind.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat these. It adds the context that this operates on 'Schema API' and 'for an asset kind,' which is a mild scoping clarification but does not disclose any additional behavioral traits such as return format, error conditions, or rate limits.

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 that is front-loaded with the tool's purpose and scoped context. Every word earns its place, with no redundancy or filler.

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 single parameter, read-only annotations, and simple nature of the tool, the description is sufficient. It clearly states what is read and the scope. The lack of an output schema is not a significant gap because the tool is a simple read, and annotations cover safety. Slightly more detail about the rules' structure would push it higher, but it is complete for typical usage.

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?

The schema fully documents the sole parameter 'kind' with description 'Asset kind,' so schema coverage is 100%. The description's phrase 'for an asset kind' adds no extra meaning beyond the schema. It does not explain allowed values, relationships, or usage nuances, but with full schema coverage the baseline of 3 is appropriate.

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 specifies a read operation for Identification/Reconciliation Engine rules scoped to an asset kind. The 'Schema API' prefix distinguishes it from the sibling tool ucontrol_read_umap_ire_rules, which likely targets umap instead. This is a specific verb+resource+scope that leaves little ambiguity.

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. It does not mention that this reads schema-level rules while ucontrol_read_umap_ire_rules handles umap rules, nor any prerequisites or exclusions. Users must infer usage from the tool naming alone.

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