Skip to main content
Glama
Sign In
CNB Remote MCP

CNB Remote MCP

by htazq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get build stage logs

build_stage_logs
Read-onlyIdempotent

Retrieve the log for a specific pipeline stage using IDs from build_status; output is truncated to keep responses small.

Instructions

Get the log of one pipeline stage. Find pipelineId/stageId via build_status first. Log output is truncated to keep responses small.

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": {
      "repo": "<repo>",
      "sn": "<sn>",
      "pipeline_id": "<pipeline_id>",
      "stage_id": "<stage_id>"
    },
    "name": "build_stage_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
snYesBuild SN
repoYesRepository path, e.g. "owner/repo" or "group/subgroup/repo"
stage_idYesStage ID from build_status
max_charsNoMax log characters to return (default 60000)
pipeline_idYesPipeline ID from build_status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the truncation disclosure — an important behavioral trait an agent would otherwise not anticipate. It stops short of saying how truncation is signalled in the response or that max_chars controls it.

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?

Three short sentences, front-loaded with the core action, then the prerequisite, then the behavioral caveat. Nothing is wasted or repeated.

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 read-only log fetch with a fully documented schema and no output schema, the description covers purpose, prerequisite, and the key truncation caveat. Minor gaps remain around what a truncated response looks like and behavior when a stage has no logs.

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%, so every parameter including max_chars and the default of 60000 is already documented. The description's mention of pipelineId/stageId merely restates the schema's "from build_status" notes, adding no new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — retrieving the log of one pipeline stage — which is clearly distinct from the status-oriented siblings. It does not explicitly say how it differs from build_status beyond the ID look-up hint, so it falls just short of the top mark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Find pipelineId/stageId via build_status first" gives an explicit prerequisite and names the sibling to call beforehand. There is no when-not guidance or error-path advice, but the sequencing guidance is concrete.

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