Skip to main content
Glama
Sign In
CST-MCP

CST-MCP

by woson-L
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cst_runtime_detect_tool

Reports the built-in runtime command bridge and available commands, so MCP clients can detect CST Studio Suite automation runtime capabilities before configuring or running jobs.

Instructions

Report the built-in runtime command bridge and its commands.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cst_runtime_detect_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether the operation is read-only, what happens if the runtime bridge is unavailable, or any permission or side-effect characteristics. The output schema covers return values, but behavioral traits remain unspecified.

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, front-loaded sentence with no wasted words. It states the purpose immediately and is appropriately sized for a zero-parameter detection tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has no parameters, and has an output schema, so the description need not explain return values. However, in the context of many closely related runtime_* siblings, it omits the routing information an agent needs to select it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and 100% schema coverage. With no parameters to document, the baseline is 4; the description cannot add further parameter 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?

The description states a clear verb and resource: 'Report the built-in runtime command bridge and its commands.' It is more specific than a tautology, but it does not differentiate this tool from nearby siblings such as cst_runtime_describe_tool, cst_runtime_list_tools_tool, or cst_runtime_usage_guide_tool.

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

Usage Guidelines2/5

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

No when-to-use guidance is provided. The description does not explain when an agent should call this detect tool instead of the other runtime discovery tools, nor does it state prerequisites or exclusions.

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