Skip to main content
Glama
Sign In
vtkapi-mcp

vtkapi-mcp

by patrickoleary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vtk_search_classes

Search for VTK classes by name or keyword to find the correct class for your VTK Python scripts.

Instructions

Search for VTK classes by name or keyword

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": {
      "query": "<query>"
    },
    "name": "vtk_search_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch term (e.g., 'reader', 'mapper', 'actor')
limitNoMaximum number of results (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior1/5

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

No annotations provided, and the description does not disclose any behavioral traits such as read-only, side effects, rate limits, or result properties. With no annotations, the description fails to inform the agent about operational behavior.

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?

Single sentence with 8 words, no redundancy. However, it could include more context without becoming verbose. Slightly under-informative for a search tool.

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

Completeness2/5

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

Given the simplicity and sibling context, the description lacks details on result ordering, matching behavior, and how it fits into the workflow of using other VTK tools. Incomplete for optimal agent decision-making.

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 parameters are already documented. Description adds minimal value by noting 'by name or keyword', which aligns with the query parameter. Baseline 3 is appropriate.

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?

Description clearly states 'Search for VTK classes by name or keyword' with verb 'search' and resource 'VTK classes'. It distinguishes from sibling tools which retrieve specific class details.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like vtk_get_class_info or vtk_validate_import. Lacks context about prerequisites or recommended order.

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