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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_pipeline_history_detail

Read-only

Retrieve detailed execution history for a specific pipeline run using the project ID and history ID, enabling you to investigate failures, review logs, and understand run outcomes.

Instructions

Get detailed execution history for a specific pipeline run

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>",
      "historyId": "<historyId>"
    },
    "name": "ncloud_get_pipeline_history_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
historyIdYesExecution history ID
projectIdYesPipeline ID

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?

The readOnlyHint annotation already indicates a safe read operation. The description adds minimal behavior beyond that—it does not disclose response format or any constraints, but for a simple get-detail tool this is acceptable.

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, focused sentence with no filler, front-loading the action and object clearly.

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 endpoint with two well-documented parameters, the description is adequately complete. It could specify the content of the returned history (e.g., stages, logs), but the absence of an output schema makes this less critical.

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?

The input schema covers 100% of the parameters with meaningful descriptions ('Execution history ID' and 'Pipeline ID'). The tool description does not add extra parameter context, so the baseline score of 3 applies.

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 uses a specific verb ('Get') and resource ('detailed execution history for a specific pipeline run'), which clearly identifies the tool's function. It distinguishes itself from list-style tools like ncloud_list_pipeline_history by emphasizing 'specific pipeline run'.

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 the tool is for retrieving details of a particular pipeline run, but it does not explicitly state when to use it versus listing histories or getting pipeline definitions, nor does it mention alternative 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