Schema | touchdesigner-manual

touchdesigner-manual

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
browse_manualA	L0 - list page sections to orient before retrieving full passages. `Cheapest way to discover the wiki's own vocabulary — the best recovery move when a search misses. Prefer this over search_manual when you need the shape of a topic rather than a specific answer. Args: query: Optional keywords to filter section headings and page titles. family: Optional operator family filter — TOP, CHOP, SOP, DAT, MAT, COMP, POP. limit: Maximum sections to list.`
search_manualA	L1 - find passages answering a question, with wiki-URL citations. Runs BM25 and dense retrieval, fuses with Reciprocal Rank Fusion, rescores with a cross-encoder. If the top score signals a probable miss, a second HyDE pass fires automatically. Handles exact operator/parameter names and paraphrased questions alike. Args: query: What you need to know. family: Optional operator family scope — TOP, CHOP, SOP, DAT, MAT, COMP, POP. Use it when the question is about one family's operator; same-named operators exist across families. limit: Maximum passages to return.
read_pageA	L2 - read the full markdown of one wiki page, or one of its sections. `Use after search_manual or browse_manual to get surrounding context. Titles are exact wiki titles, e.g. "Noise TOP", "CHOP Execute DAT", "noiseTOP Class". Args: title: Exact wiki page title. section: Optional section heading to return just that section.`

browse_manualA

L0 - list page sections to orient before retrieving full passages.

Cheapest way to discover the wiki's own vocabulary — the best recovery move
when a search misses. Prefer this over search_manual when you need the
shape of a topic rather than a specific answer.

Args:
    query: Optional keywords to filter section headings and page titles.
    family: Optional operator family filter — TOP, CHOP, SOP, DAT, MAT, COMP, POP.
    limit: Maximum sections to list.

search_manualA

L1 - find passages answering a question, with wiki-URL citations.

Runs BM25 and dense retrieval, fuses with Reciprocal Rank Fusion, rescores
with a cross-encoder. If the top score signals a probable miss, a second
HyDE pass fires automatically. Handles exact operator/parameter names and
paraphrased questions alike.

Args:
    query: What you need to know.
    family: Optional operator family scope — TOP, CHOP, SOP, DAT, MAT, COMP, POP.
        Use it when the question is about one family's operator; same-named
        operators exist across families.
    limit: Maximum passages to return.

read_pageA

L2 - read the full markdown of one wiki page, or one of its sections.

Use after search_manual or browse_manual to get surrounding context.
Titles are exact wiki titles, e.g. "Noise TOP", "CHOP Execute DAT",
"noiseTOP Class".

Args:
    title: Exact wiki page title.
    section: Optional section heading to return just that section.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
`manual_index`	Corpus size, operator counts per family, and index freshness.

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored 2026-08-03 23:30 across 3 tools

Disambiguation4/5

The three tools are mostly distinct: browse_manual for orientation/discovery, search_manual for finding passages, and read_page for reading full content. The browse_manual and search_manual could potentially overlap when searching for a specific topic (both filter by family and query), but the descriptions clearly differentiate them by cost tier and use case, so an agent can usually tell them apart.

Naming Consistency4/5

The tool names follow a consistent verb_noun pattern (browse_manual, search_manual, read_page), all snake_case. Slight inconsistency in that browse_manual and search_manual both target 'manual' while read_page targets 'page', but the pattern is predictable and readable overall.

Tool Count4/5

Three tools is a reasonable count for a documentation/manual retrieval server. It's on the lean side but each tool serves a distinct retrieval stage (discover, search, read). Given the narrow scope of a documentation lookup server, three well-chosen tools feel appropriate, though it borders on thin.

Completeness3/5

The core browse-search-read workflow is covered and represents the essential operations for a wiki documentation server. However, there are minor gaps: no way to list all pages in a family without a query, no direct tool for navigating to a specific page by title from scratch (read_page requires knowing the exact title), and no distinction between getting a section vs. full page could be improved. These are workable gaps but notable.

Maintenance

ActivityStale

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers