ucontrol-mcp

Ucontrol Read Umap Sso Group Details

ucontrol_read_umap_sso_group_details

Read-onlyIdempotent

Retrieves SSO group details from the uMap API. Provides access to group information for authentication and authorization processes.

Instructions

uMap API: read SSO group details.

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_sso_group_details"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

B3.3/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, covering the safety profile. The description does not add any behavioral context beyond the annotations, such as return format or side effects, but the annotations sufficiently indicate a safe read operation. No contradiction is present.

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?

The description is extremely concise with a single sentence and no fluff. It provides the essential resource identifier. However, it borders on under-specification, though that is more of a completeness issue than a structure issue.

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?

For a zero-parameter read tool with rich annotations, the description is minimally adequate. It does not mention what the 'SSO group details' contain or any potential context like authentication requirements, but the absence of parameters and the safety annotations reduce the need for additional context. Still, a more descriptive phrase would improve completeness.

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?

The input schema has zero parameters, so there is no parameter-level information needed. The description need not explain parameters, and the baseline for 0 params is 4.

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 clearly states a specific verb ('read') and resource ('SSO group details'), which distinguishes it from sibling tools like 'read_umap_team_details' or 'read_umap_model_details'. However, it is minimalist and does not elaborate on what 'details' includes, so it does not fully communicate the scope.

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?

The description provides no guidance on when to use this tool versus alternative read tools (e.g., team details or model details). There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage solely from the resource name.

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