Skip to main content
Glama

ncp_call

Read-only

Call read-only Ncloud APIs with signed requests. Query servers, VPCs, billing, or subaccounts, filter fields, and auto-paginate list results without per-API tool setup.

Instructions

Call one read-only Ncloud API (get*/list*/describe*/... or REST GET) with request signing.

Args: service: Ncloud service key, e.g. 'vserver', 'vpc', 'vloadbalancer', 'vpostgresql', 'billing', 'subaccount'. Unknown names map to the shared gateway //v2. action: Path under the service base, e.g. 'getServerInstanceList' or '/sub-accounts'. params: Query parameters. Lists become name.1, name.2; dicts become name.key. fields: Keep only these keys in each list item (dot paths allowed, e.g. ['serverName', 'serverInstanceStatus.code']). profile: Credential profile. Required when more than one profile exists. paginate: Follow pageNo until totalRows is reached for list actions.

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": {
      "service": "<service>",
      "action": "<action>"
    },
    "name": "ncp_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
fieldsNo
paramsNo
profileNo
serviceYes
paginateNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: request signing is performed, unknown service names fall back to the shared gateway /<service>/v2, and pagination follows pageNo until totalRows for list actions.

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 opening sentence front-loads purpose and the read-only constraint, and each subsequent line maps to one parameter with no filler. The Args-block formatting is slightly mechanical but every line earns its place.

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?

Output schema exists, so return values need not be explained, and the description covers naming, path construction, flattening, projection, credentials, and pagination for a six-parameter open-world tool. Minor gaps remain around error behavior and whether write verbs are rejected outright.

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

Parameters5/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 and does so for all six parameters. It explains path composition for action, list/dict flattening syntax for params (name.1, name.key), dot-path projection for fields, and the conditional requirement for profile.

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?

States a specific verb and resource: call one read-only Ncloud API, with the accepted verb patterns (get*/list*/describe* or REST GET) and request signing called out. An agent can tell this is a single-call passthrough rather than a multi-operation tool, though siblings (ncp_batch, ncp_profiles) are never named to sharpen the distinction.

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 read-only scope is explicit and therefore implies when the tool applies, and the profile note ('Required when more than one profile exists') gives one concrete precondition. There is no explicit when-not guidance, no mention of what to do for write operations, and no routing to alternatives for bulk work.

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