Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NCLOUD_ZONENoNcloud zone (pub, gov, or fin) used with NCLOUD_ACCESS_KEY and NCLOUD_SECRET_KEY to add an env-<zone> profile.
NCP_MCP_CONFIGNoPath to the Ncloud configuration file. Defaults to ~/.ncloud/configure.
NCP_ALLOW_WRITENoSet to true to register the ncp_write tool for create, update, and delete API calls. By default only read-only tools are available.
NCLOUD_ACCESS_KEYNoNcloud access key ID used to add an env-<zone> profile when NCLOUD_SECRET_KEY and NCLOUD_ZONE are also provided.
NCLOUD_SECRET_KEYNoNcloud secret access key used to add an env-<zone> profile when NCLOUD_ACCESS_KEY and NCLOUD_ZONE are also provided.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

NAVER Cloud Platform (Ncloud) API access through signed generic calls. Credential profiles (name ends with its zone pub/gov/fin): (none configured). When more than one profile exists, every call must name its profile; pick the one that matches the account the user is asking about and ask the user if unsure. ncp_profiles(verify=true) shows which NCP account/user each key really belongs to. Shared-gateway services use https://ncloud.apigw.//v2/ (e.g. service='vserver', action='getServerInstanceList'); responseFormatType=json is added automatically. List parameters are passed as JSON arrays and are expanded to name.1, name.2. ncp_call and ncp_batch are read-only. ncp_write exists only when the server is started with NCP_ALLOW_WRITE=true. Use 'fields' to keep only the columns you need from large list responses.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ncp_profilesA

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.

ncp_callA

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.

ncp_batchA

Run several read-only ncp_call requests concurrently; results keep the input order.

Each item takes the ncp_call keys: service, action, and optionally params, fields, profile, paginate. A per-item 'profile' overrides the batch profile. Failures are reported per item and do not stop the others.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation4/5

Each tool targets a distinct layer: ncp_profiles for credential/config inspection, ncp_call for a single API request, and ncp_batch for concurrent multi-request execution. The only mild overlap is that ncp_batch is effectively a fan-out wrapper over ncp_call, but the descriptions make the boundary clear (order-preserving, per-item failure isolation, per-item profile override).

Naming Consistency4/5

All names share a consistent ncp_ prefix and snake_case form, which reads well as a family. The only minor deviation is that ncp_profiles is a noun while ncp_call and ncp_batch are verbs, but the intent of each is still immediately clear.

Tool Count4/5

Three tools is lean but appropriate for a generic gateway design, where the breadth lives inside ncp_call's service/action arguments rather than in separate tools. Nothing feels redundant or missing at the tool level, though the surface is on the thin side.

Completeness3/5

The read-only call/batch pair covers querying well, including pagination, field filtering, and credential selection. However, there is no discovery/introspection tool to enumerate available services and actions (or their schemas), so an agent must already know Ncloud API paths, and no write operations are exposed despite the mention of a writes-enabled flag.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues