List CST Studio VBA objects, optionally filtered by category. Get object names with descriptions to locate the right scripting object for automation.
List available CST Studio VBA objects, optionally filtered by category. Returns object names with brief descriptions.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Optional category filter. If omitted, all categories are returned. |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It indicates a read-only query (list operation) with no side effects, but does not explicitly state safety, permissions, or limitations. The description is adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with two clauses, efficiently communicating purpose, filtering, and output. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with one optional parameter and no output schema, the description adequately covers the return format (names with descriptions) and filtering. It is complete enough for the agent to use effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%; the description adds minimal value by restating the filtering option. It does not elaborate on the category values or parameter behavior beyond what the schema provides. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it lists CST Studio VBA objects, specifying optional filtering by category and noting the return of names with descriptions. This distinguishes it from sibling tools like cst_list_materials or cst_list_ports, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for discovering available VBA objects, especially with filtering. However, it lacks explicit guidance on when not to use it or alternatives. Given the context, it provides clear context but no exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.