Skip to main content
Glama
Sign In
vtkapi-mcp

vtkapi-mcp

by patrickoleary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vtk_get_method_doc

Retrieve the documentation string for a specific method of a VTK class. Validate method existence and return its docstring.

Instructions

Get just the docstring for a specific method of a 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>",
      "method_name": "<method_name>"
    },
    "name": "vtk_get_method_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
class_nameYesVTK class name
method_nameYesMethod name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, error handling, or return value behavior. It only states the functional purpose, which is insufficient for full transparency.

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 concise sentence that is front-loaded and contains no wasted words. It is appropriately sized for the simple functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with only two parameters and a straightforward purpose, the description is largely adequate. However, it does not specify the return type (e.g., string) or error behavior, which would improve completeness.

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 description coverage is 100%, so the parameters are already well-described. The description adds no additional meaning beyond the schema, resulting in a baseline score of 3.

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 that the tool retrieves the docstring for a specific method of a VTK class, using a specific verb and resource. It distinguishes itself from sibling tools like vtk_get_method_info and vtk_get_method_signature by emphasizing 'just the docstring'.

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 that the tool should be used when only the docstring is needed, but it does not explicitly contrast with sibling tools or provide when-not-to-use guidance. The usage is implied but not fully specified.

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