vtkapi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_DOCS_PATH | No | Path to the VTK Python docs JSONL file (default: data/vtk-python-docs.jsonl). Pass via --api-docs command-line argument. | data/vtk-python-docs.jsonl |
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 |
|---|---|
| vtk_get_class_infoB | Get complete information about a VTK class including module path, description, and methods |
| vtk_get_class_methodsA | List all methods (with signatures) for a VTK class and optionally verify a specific method |
| vtk_search_classesC | Search for VTK classes by name or keyword |
| vtk_get_class_moduleA | Return the vtkmodules.* import path for a given VTK class |
| vtk_get_module_classesC | List all VTK classes in a specific module |
| vtk_validate_importC | Validate if a VTK import statement is correct and suggest corrections |
| vtk_get_method_infoB | Get documentation for a specific method of a VTK class |
| vtk_get_method_docA | Get just the docstring for a specific method of a VTK class |
| vtk_get_method_signatureA | Return only the canonical signature for a specific method of a VTK class (minimal payload) |
| vtk_get_class_docB | Get the class documentation string for a VTK class |
| vtk_get_class_synopsisA | Get a brief synopsis/summary of what a VTK class does |
| vtk_get_class_action_phraseB | Get the action phrase describing what a VTK class does (e.g., 'data reading', 'mesh filtering') |
| vtk_get_class_roleA | Get the pipeline role of a VTK class. Returns one of: input, filter, properties, renderer, scene, infrastructure, output, utility, color |
| vtk_get_class_visibilityA | Get the visibility score of a VTK class (0.0-1.0). Higher scores indicate classes more likely to be used directly. |
| vtk_get_class_input_datatypeA | Get the input data type for a VTK class (e.g., 'vtkPolyData', 'vtkImageData') |
| vtk_get_class_output_datatypeA | Get the output data type for a VTK class (e.g., 'vtkPolyData', 'vtkImageData') |
| vtk_get_class_semantic_methodsA | Get non-boilerplate callable methods for a VTK class. Excludes dunder methods, private methods, and VTK infrastructure methods. |
| vtk_is_a_classA | Check if a given name is a valid VTK class. Returns true if it exists in the VTK API, false otherwise. |
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 18 tools
Each tool has a clearly distinct purpose, querying different aspects of VTK classes (e.g., action phrase, doc, methods, module). Overlaps are minimal and well-defined (e.g., three method-query tools differentiate by payload: doc only, doc+signature, signature only).
All tools follow a consistent snake_case pattern with 'vtk_' prefix, verb (mostly 'get', plus 'is_a', 'search', 'validate'), and specific resource. Naming is predictable and uniform.
With 18 tools, the set is well-scoped for a reference API server that provides detailed class metadata. Each tool serves a clear need without clutter.
The tool surface covers all key aspects of VTK class information: identification, documentation, methods, module path, input/output types, role, visibility, search, import validation, and per-module listing. No obvious gaps for the stated purpose.