Skip to main content
Glama
Sign In
tdmcp

tdmcp

by lucasmaher-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List TD Python classes

get_td_classes
Read-only

Lists TouchDesigner Python API class names from an offline knowledge base. Filter by name to find relevant classes for building or controlling TD networks.

Instructions

Read-only: list TouchDesigner Python API class names from the embedded knowledge base (works offline, never touches TD). Returns {classes[]} of name/displayName entries. Optionally filter by name. Use get_td_class_details or get_module_help to expand one class into its members and methods.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_td_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoOptional case-insensitive substring to filter class names by.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, and the description adds valuable context beyond that: it says the tool works offline and never touches TD, which is more specific than a generic read-only hint. It also discloses the return shape ({classes[]}), enhancing behavioral 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 three sentences with no wasted words. It front-loads 'Read-only' and each sentence provides distinct value: purpose, behavior/return format, and alternative tool guidance.

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

Completeness5/5

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

For a simple list tool with one optional parameter and clear annotations, this description is complete. It covers what it does, safety profile (offline/read-only), return format, and how to proceed for more detail, without needing an output schema.

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% for the single 'filter' parameter, which already includes a description ('case-insensitive substring'). The description's 'Optionally filter by name' adds minimal extra meaning, so the baseline of 3 is appropriate—schema does the heavy lifting.

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 lists TouchDesigner Python API class names from the embedded knowledge base, with a specific verb ('list') and resource ('class names'). It also explicitly distinguishes from siblings by pointing to get_td_class_details and get_module_help for expansion, making its purpose unique.

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

Usage Guidelines5/5

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

The description provides explicit guidance: use this tool for listing class names, and use get_td_class_details or get_module_help to expand a class into members/methods. It also notes that it works offline and never touches TD, giving clear context for when it's appropriate to invoke.

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