Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bw_processchain_logs

Retrieve process chain execution logs and current run status. Use limit, offset, or outputPath to control pagination and full log output.

Instructions

Get process chain execution logs and current run status. Defaults to the most recent log entries; use limit/offset to page, or outputPath for the full log set. Response shape: { logs, status, ...paging }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
limitNoMax entries returned inline (default 100).
offsetNo
outputPathNoIf provided, the full result is written to this path (under the workdir) and the tool returns only a small summary envelope { ok, outputPath, bytes, summary }. Objects/arrays are written as JSON; ONLY the bw_*_get_xml family writes the raw XML string as plain text (that file is directly reusable as xmlPath in a later save call). Other *_get tools (e.g. bw_dtp_get, bw_trfn_get) write the PARSED XML-to-JSON tree, not raw XML — use the matching bw_*_get_xml tool when you need the raw XML string. Use outputPath for large responses (XML, table data, logs, dataflow graphs). When set, tools skip inline pagination/projection so the file contains the complete payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does well by revealing default behavior, paging behavior, the outputPath full-payload behavior, and the response envelope. It does not mention error or auth behavior, but for a read-oriented log tool this is a minor gap.

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 two tight sentences with no filler. The first sentence states purpose and default behavior; the second covers paging and outputPath. Every sentence 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 log retrieval tool with no annotations and no output schema, the description supplies essential context: response shape, default recency, paging, and the full-output alternative. It could explicitly say that id identifies the process chain, but the tool name and sibling context make that low-risk. Overall, it is sufficiently complete for correct invocation.

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 50%: limit and outputPath have schema descriptions, while id and offset do not. The tool description partially compensates by framing limit/offset as paging and outputPath as the full log set, but id is still left to inference. The lengthy outputPath schema text carries most of that parameter's meaning, so the description adds grouping rather than complete definitions.

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 opens with a specific verb and resource: 'Get process chain execution logs and current run status.' This clearly distinguishes it from sibling tools like bw_processchain_execute, bw_processchain_stop, or bw_processchain_details, and it names an expected response shape. It is non-tautological and immediately actionable.

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?

The description gives practical usage guidance: it defaults to the most recent log entries, supports limit/offset paging, and offers outputPath for the full log set. It does not explicitly compare against sibling tools, but the intended contexts are clear enough for selection and invocation.

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