Skip to main content
Glama

ncp_profiles

Read-only

Lists usable and disabled credential profiles with reasons and write status; optionally verifies usable profiles via NCP STS to show account ID, login alias, and user type without exposing secrets.

Instructions

List usable credential profiles, disabled profiles with the reason, and whether writes are enabled.

Secrets are never returned. With verify=true, each usable profile is checked against NCP STS (GET /api/v1/caller-identity) and the key owner's account id, login alias and user type (Customer = main account, Sub = sub account, Role) are shown.

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": "ncp_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
verifyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, but the description adds meaningful context beyond them: secrets are never returned, disabled profiles expose a reason, and verify=true triggers a live call to NCP STS (GET /api/v1/caller-identity) with account id, login alias and user type surfaced. The open-world outbound call is the single most valuable disclosure here and it is stated plainly.

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?

Two short paragraphs, front-loaded with the core behavior and the security guarantee, followed by the opt-in verification detail. No filler sentences, and every clause conveys information the agent would otherwise have to guess.

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?

With an output schema present, the description needn't document return shapes, and it is complete on the read-only safety profile and the one parameter's effect. Minor gaps remain — no note on how a 'disabled' profile differs operationally or whether listing is account-scoped — but nothing essential to correct invocation is missing.

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 description coverage is 0%, so the description carries the full burden for the lone `verify` parameter — and it does explain what setting it to true causes (per-profile STS identity check) and what extra fields then appear. It does not state the default (false) or that verification costs one network round trip per profile, which keeps it short of a 5.

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 opens with a specific verb and resource — list credential profiles — and enumerates what is returned: usable profiles, disabled profiles with reasons, and whether writes are enabled. It is clear what the tool does, though it never mentions the sibling tools (ncp_call, ncp_batch) to draw the boundary between listing credentials and using them.

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?

Usage is only implied: an agent can infer this is the discovery step before ncp_call, and the verify=true sentence sketches an optional verification flow. There is no explicit when-to-use vs. when-not-to-use statement, no mention of a prerequisite ordering relative to ncp_call, and no cost warning for verify.

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

Deploy Server

Other Tools