Skip to main content
Glama
Sign In
vtkapi-mcp

vtkapi-mcp

by patrickoleary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vtk_get_class_methods

Retrieve all methods and signatures of a VTK class, or verify if a specific method exists.

Instructions

List all methods (with signatures) for a VTK class and optionally verify a specific method

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

Input Schema

NameRequiredDescriptionDefault
class_nameYesVTK class name
method_nameNoOptional method to verify existence

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 states the tool lists methods with signatures, which is a read operation. However, it omits details like error handling, whether inherited methods are included, or output format, leaving some ambiguity.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that captures the main purpose and optional behavior. It contains no unnecessary words and effectively communicates the tool's function.

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?

The description is functional but incomplete. It does not specify whether methods include inherited, protected, or private ones, nor the exact behavior of the method_name verification (e.g., exact match). Given the simplicity of the tool, more context would improve usability.

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 baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions ('VTK class name' and 'Optional method to verify existence'). The description itself does not elaborate further.

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 uses a specific verb 'List' and clearly identifies the resource 'methods (with signatures) for a VTK class'. It also mentions an optional verification function, which distinguishes it from sibling tools like vtk_get_method_signature or vtk_get_method_info that focus on single methods.

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 usage scenarios (listing all methods or verifying one), but lacks explicit guidance on when to choose this tool over alternatives, prerequisites like a valid class name, or constraints such as case sensitivity for method verification.

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