Skip to main content
Glama
Sign In
CST-MCP

CST-MCP

by woson-L
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cst_tool_manifest_tool

Return the full machine-readable manifest of the CST MCP server to inspect its available tools. Optionally write the manifest to a file via out_path.

Instructions

Return the full machine-readable manifest of the CST MCP (write it to a file with out_path).

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_tool_manifest_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
out_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It mentions that the manifest can be written to a file via out_path, but does not describe what happens if out_path is omitted, whether the manifest is also returned inline, or any side effects like file overwrites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that efficiently conveys the core action and the optional file output. It could be slightly more structured by clarifying the dual return/write behavior, but it avoids waste.

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 simplicity, one parameter, and the presence of an output schema, the description covers the basics. However, the interaction between out_path and the tool's return value remains ambiguous, and no annotations exist to fill that gap.

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 0%, so the description must compensate for the single out_path parameter. It does so by stating 'write it to a file with out_path', which clarifies the parameter's purpose, but it does not explain the default null behavior or whether the manifest is returned when out_path is not provided.

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 ('Return') and resource ('full machine-readable manifest of the CST MCP'), which clearly distinguishes it from list-oriented siblings like cst_list_mcp_tools_tool. However, it does not explicitly differentiate itself from those siblings or mention alternatives.

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 guidance on when to use this tool versus alternatives such as cst_list_mcp_tools_tool or cst_toolbox_list_tools_tool. It only implies usage through the stated purpose, leaving the agent to infer context.

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