ucontrol-mcp

Ucontrol Read Umap Models

ucontrol_read_umap_models

Read-onlyIdempotent

List uMap models from the uMap API with pagination support to retrieve model data for uControl operations.

Instructions

uMap API: list models.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ucontrol_read_umap_models"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`size`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

C2.7/5.0

Behavior2/5

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

The description only repeats the read-only nature ('list') which is already covered by the annotations. It adds no new behavioral traits like pagination behavior, return format, or scoping constraints. No contradiction with annotations.

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 with no filler. It is appropriately sized for the simplicity of the operation, though it sacrifices completeness (see other dimensions).

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?

With no output schema and sparse description, the agent has no idea what the response structure is, what pagination entails, or how this relates to sibling tools. The description is too brief to be complete for a tool with optional parameters.

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

Parameters1/5

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

The schema has 0% description coverage for its two parameters (page, size), and the description does not mention them at all. The agent receives no explanation of what these parameters mean or how to use them, leaving a gap the description should have filled.

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 a specific action ('list') and resource ('models'), making the tool's purpose clear. It is distinct from siblings like 'read_umap_model_details' by indicating a collection operation, though it does not explicitly reference alternatives.

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?

There is no guidance on when to use this tool versus alternatives such as 'ucontrol_read_umap_model_details' or other read tools. The description does not mention any context or exclusions.

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