ucontrol-mcp

Ucontrol Read Umap Model Patterns

ucontrol_read_umap_model_patterns

Read-onlyIdempotent

List discovery patterns linked to a uMap model. Provide the uMap ID to retrieve associated patterns.

Instructions

uMap API: list discovery patterns linked to a uMap model.

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": {
      "uMapId": "<uMapId>"
    },
    "name": "ucontrol_read_umap_model_patterns"
  }
}

Input Schema

Name	Required	Description	Default
`uMapId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds the scoping constraint that results are linked to a specific uMap model, which is useful context, but no additional behavioral details such as return format or pagination are provided.

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 concise sentence, front-loads the API context, and contains no superfluous content.

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?

For a simple read tool with one parameter and no output schema, the description adequately conveys the operation's scope. It lacks detail on the structure of patterns, but given the domain-specific language and annotations, it is sufficiently complete for basic invocation.

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 sole parameter uMapId is not described in the schema, and description only implicitly identifies it as the uMap model identifier via 'linked to a uMap model.' This provides some meaning but lacks format, source, or usage examples.

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 lists discovery patterns linked to a uMap model, using a specific verb and resource. It distinguishes from siblings like ucontrol_read_umap_model_details by focusing on patterns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description provides no explicit when-to-use or alternative guidance, but the phrasing implies it's for retrieving discovery patterns for a specific uMap model. Siblings exist but no exclusion criteria are given.

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