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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_pipeline

Read-only

Retrieve detailed configuration of a SourcePipeline pipeline, including its tasks and triggers, by supplying the pipeline project ID.

Instructions

Get detailed information about a specific SourcePipeline pipeline including tasks and triggers

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": {
      "projectId": "<projectId>"
    },
    "name": "ncloud_get_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesPipeline ID (from ncloud_list_pipelines)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotation readOnlyHint=true already indicates safety, and the description adds that the output includes tasks and triggers, which is useful context. However, it does not disclose other behavioral aspects like return format, potential errors, or permissions, though the read-only nature is covered.

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 is front-loaded with the action and resource, followed by relevant detail about what information is included. There is no redundant wording or unnecessary information.

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 get-by-ID tool with one parameter and no output schema, the description is adequate. It conveys the purpose, the needed input, and the expected content (tasks and triggers). Given the low complexity, no additional context is essential, though a note about return format could make it slightly richer.

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% and the single parameter 'projectId' is well-described in the schema ('Pipeline ID (from ncloud_list_pipelines)'). The tool description does not add further parameter details beyond what the schema provides, but the schema itself is sufficient, so a 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?

The description clearly states the action ('Get detailed information') and the resource ('a specific SourcePipeline pipeline'), with added specificity about what is included ('tasks and triggers'). This distinguishes it from sibling tools like ncloud_list_pipelines (which lists pipelines) and ncloud_get_pipeline_history_detail (which gets history details).

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 description implies usage for retrieving details of a single pipeline, and the parameter description ('Pipeline ID from ncloud_list_pipelines') provides a workflow hint. However, it does not explicitly explain when to use this tool versus alternatives such as ncloud_list_pipelines for overviews or ncloud_get_pipeline_history_detail for historical run information.

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