cnc-mcp

Get Credential Profile

cnc_get_credential_profile

Read-onlyIdempotent

Fetch a credential profile by name to obtain its user/password records with masked secrets, used for device and provider authentication.

Instructions

Get the full record of one credential profile by name.

Read-only. Profiles have no UUID: the name is the identifier everywhere (devices and providers reference it in their "profile" field). Find names with cnc_list_credential_profiles.

Args: profile: exact profile name (case-insensitive; surrounding whitespace is stripped). A '*' wildcard is accepted by the platform but this tool needs a single exact match.

Returns: str: JSON object {"profile": str, "user_pass": [{"user_name", "password": "******", "type": "ROBOT_USERPASS_SSH|HTTP|HTTPS|...", ...}], "v2_info": {...}?, "v3_info": {...}?}. Secrets are masked by the API. On failure: "Error: Credential profile '' not found ..." when nothing matches, "Error: ... matches several profiles ..." when a wildcard was used, "Error: profile must not be empty ..." for a blank name, or "Error: ".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`profile`	Yes	Exact profile name, case-insensitive (e.g. 'nso', 'cml-xrd').

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare the read-only/idempotent/non-destructive profile, but the description goes well beyond them: profiles have no UUID so the name is the identifier everywhere, secrets are masked by the API, wildcards are accepted by the platform but not by this tool, and it enumerates the exact error strings returned on failure.

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?

Front-loaded with purpose, then Read-only note, then Args and Returns sections. The enumeration of four distinct error strings is slightly verbose but each is actionable for an agent and the rest is free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers identifier model, masking behavior, wildcard caveat, and failure modes. With an output schema present, the description does not need to explain return values, and its added behavioral context leaves an agent fully equipped to call it correctly.

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?

Schema coverage is 100% and the schema already documents the single profile parameter, so the baseline is 3. The description adds real value beyond it: matching is case-insensitive, surrounding whitespace is stripped, and a '*' wildcard is accepted by the platform but rejected here – detail the schema does not convey.

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?

States a specific verb (get) and resource (credential profile) with scope 'one ... by name'. It also distinguishes itself from the sibling cnc_list_credential_profiles, so an agent can tell the two apart without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes discovery to 'Find names with cnc_list_credential_profiles' and states the condition that selects this tool: a single exact match is required. Nothing about when to use it over the list sibling is left to inference.

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