Skip to main content
Glama
Sign In
CST-MCP

CST-MCP

by woson-L
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cst_detect_tool

Detect the CST executable, automation libraries, and running Design Environments to verify setup and enable automation.

Instructions

Detect the CST executable, automation libraries and running Design Environments.

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_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 burden of behavioral disclosure. It does not state whether detection is read-only, what permissions are required, whether it has side effects, or how it performs detection. Only the purpose is given, with no additional behavioral context.

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?

A single, front-loaded sentence that efficiently conveys the tool's purpose without any redundant or filler text.

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?

Given the tool's low complexity, empty input schema, and existing output schema, the description covers the basic purpose. However, it omits any usage context or behavioral details (e.g., read-only nature, prerequisites) that would help an agent decide when to invoke it, making it minimally adequate.

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 takes zero parameters, so per the rubric baseline is 4. The schema is empty and fully covered, so no parameter semantics need to be added in the description.

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 specific verb 'Detect' and three concrete resources: CST executable, automation libraries, and running Design Environments. This is clear and distinct from generic detection tools. However, it does not explicitly differentiate itself from sibling tools like cst_runtime_detect_tool or cst_list_design_environments_tool, leaving some ambiguity about when this tool is preferred over those.

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?

The description provides no when-to-use guidance, no prerequisites, and no mention of alternatives. It only states what the tool detects, leaving the agent to infer context from the name and siblings.

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