Skip to main content
Glama
Sign In
vtkapi-mcp

vtkapi-mcp

by patrickoleary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vtk_get_class_module

Find the correct vtkmodules import path for any VTK class by providing the class name. Resolves import errors in VTK Python code.

Instructions

Return the vtkmodules.* import path for a given VTK class

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "class_name": "<class_name>"
    },
    "name": "vtk_get_class_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
class_nameYesVTK class name (e.g., 'vtkPolyDataMapper')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes a read-only operation (returning an import path) but does not disclose behavior for invalid class names or error conditions. The description is adequate but lacks details on edge cases.

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 sentence that is concise and front-loaded with the key action. However, it could be slightly more structured (e.g., clarifying the result format). Still, it is efficient.

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, no output schema), the description covers the basic purpose. However, it does not explain what a 'vtkmodules.* import path' looks like or how the result is used, leaving some ambiguity. Adequate but not thorough.

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 coverage is 100%, so the schema already documents the class_name parameter. The description adds 'VTK class' context, but this closely mirrors the schema description ('VTK class name'). Minimal added value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns the vtkmodules.* import path for a given VTK class. It uses a specific verb 'Return' and resource 'import path', effectively distinguishing it from sibling tools that provide documentation, methods, or other class info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used when the import path for a VTK class is needed, but it does not provide explicit guidance on when to use this tool versus siblings like vtk_get_class_doc or vtk_validate_import. No exclusions or alternatives are mentioned.

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