mcp-vcd
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get-signalB | Get all instances of a specified signal in a VCD file |
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 confusion between tools, so disambiguation is perfect.
A single tool trivially maintains consistency. The name 'get-signal' follows a clear verb_noun pattern.
A single tool is far too few for a VCD file server. Typical operations like loading files, listing signals, or querying multiple signals are missing.
The tool surface is severely incomplete. It only provides one operation (get-signal), lacking essential lifecycle or exploration capabilities for VCD files.