PTC-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PTC_MCP_CONFIG | No | The path to the configuration YAML file. If not set, the server looks for config.yaml in the current directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_programA | Execute a Python program with access to MCP tools as async functions. Tool calls within the script are dispatched to their respective MCP servers. Only stdout (from print statements) is returned — intermediate tool results do not enter the conversation context. Use this when a task involves 3+ tool calls, loops, filtering, aggregation, or conditional logic based on intermediate results. For single tool calls, call the tool directly. All tool functions require |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clearly defined singular purpose of executing Python programs with MCP integration.
The single tool follows a clear verb_noun naming pattern (execute_program). Since there are no other tools to compare against, consistency is inherently perfect.
One tool is too few for a server's apparent purpose of program execution with MCP integration, as it lacks complementary tools for tasks like listing available programs, managing execution environments, or handling errors. This feels thin and incomplete for the domain.
The tool surface is severely incomplete for the inferred domain of program execution and MCP tool orchestration. There are obvious gaps, such as no tools for program management, debugging, or result handling, which will limit agent capabilities and cause failures in complex workflows.