Skip to main content
Glama
Sign In
ncloud-mcp-server

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_mongodb_instance_detail

Read-only

Retrieve detailed configuration and status for a specific Cloud DB for MongoDB instance using its instance number.

Instructions

Get detailed information about a specific Cloud DB for MongoDB instance

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": {
      "cloudMongoDbInstanceNo": "<cloudMongoDbInstanceNo>"
    },
    "name": "ncloud_get_mongodb_instance_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudMongoDbInstanceNoYesCloud MongoDB instance number to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, and the description does not contradict that. However, the description adds no extra behavioral context beyond restating the tool's purpose; it does not describe the response format, any filtering constraints, or other operational details.

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?

The description is a single, concise sentence with no filler. It is front-loaded with the primary action and resource, and every word 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?

For a simple read-only detail tool with a single required parameter and no output schema, the description combined with the schema and annotations provides adequate context. It clearly indicates what the tool does, and the parameter schema covers the input. No major gaps.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'cloudMongoDbInstanceNo' described as 'Cloud MongoDB instance number to query'. The description adds no additional parameter semantics, but because the schema fully documents the parameter, baseline of 3 is appropriate.

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?

The description clearly states the action ('Get detailed information') and the resource ('specific Cloud DB for MongoDB instance'). It distinguishes from list tools (e.g., ncloud_list_mongodb_instances) and other database detail getters (e.g., ncloud_get_mysql_instance_detail).

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?

No explicit guidance on when to use this tool vs alternatives. It does not mention that listing instances is the prerequisite or that similar tools exist for other database types. Usage context is only implied by the word 'specific'.

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