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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_dataforest_get_app_detail

Read-only

Retrieve detailed information for a Data Forest app by its ID. Get the current state, components, and links to monitor and manage the app effectively.

Instructions

Get detailed information of a Data Forest app (state, components, links)

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": {
      "id": "<id>"
    },
    "name": "ncloud_dataforest_get_app_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesApp unique identifier (Base62-encoded UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so the tool is known to be read-only. The description adds that it returns 'state, components, links', which provides some behavioral context but does not elaborate on potential side effects or authorization needs beyond what annotations suggest.

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 that directly states the tool's purpose and the type of information returned. Every word is necessary; no fluff.

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?

Given low complexity (1 parameter, no output schema), the description adequately covers purpose and output. It could benefit from clarifying what 'components' and 'links' refer to, but overall sufficient for an agent to understand when to invoke it.

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 coverage is 100% for the single parameter 'id'. The description does not add any semantic detail beyond the schema's description of the parameter as 'App unique identifier (Base62-encoded UUID)'. Baseline 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?

Description clearly states the tool gets detailed information of a Data Forest app, listing specific attributes (state, components, links). The verb 'Get' and resource 'app detail' are specific and distinguish it from sibling tools like list_apps or get_app_basic_setting.

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?

No explicit when-to-use or when-not guidance is provided. The tool's purpose is implied as a standard detail retrieval for a specific app, but it doesn't mention alternatives or exclusions among similar Data Forest tools.

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