Skip to main content
Glama

Generate library index

generate_library_index

Creates a Markdown contact-sheet index of vault assets with thumbnail, title, tags, and copy-paste load snippet. Filter by category or query string.

Instructions

Write one Markdown contact-sheet note of the whole vault library — recipes, shaders, presets, components, and setlists — as a grid of cards, each with its thumbnail (the .png sibling written by save_recipe_to_vault / save_component_to_vault), title, tags, and a copy-paste load snippet (e.g. apply_recipe id=…). No TouchDesigner connection required: it reads the local vault on disk and writes the index note. Filter by category (kinds) and/or a substring query. Requires a configured TDMCP_VAULT_PATH.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindsNoWhich library categories to include. 'all' = every category.
outputNoVault-relative path of the contact-sheet note to write.Library Index.md
include_thumbnailsNoEmbed each asset's <stem>.png sibling when present; false = text-only.
columnsNoCards per row in the contact-sheet grid.
queryNoCase-insensitive substring filter on title/tags.
overwriteNoWhen false, refuse to overwrite an existing index note.
Behavior4/5

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

Annotations provide basic hints (not read-only, not destructive, open-world). The description adds valuable behavioral details: it reads the local vault from disk, writes a file, and requires a configured TDMCP_VAULT_PATH. It also describes the output format and thumbnail source, aiding the agent in understanding side effects.

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?

The description is a single, well-structured paragraph that front-loads the main action. It covers key points without excessive verbosity, though could be slightly more scannable.

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?

Given the complexity (6 parameters, no output schema) and annotations present, the description provides adequate context: output format, dependencies, prerequisites, and filtering. It does not explain the return value, but the action of writing a file is clear.

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% with all parameters described. The description mentions filtering by kinds and query but does not add significant new meaning beyond the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it writes a Markdown contact-sheet note of the vault library with thumbnail cards, title, tags, and load snippets. The purpose is specific and distinct from siblings, though it does not explicitly differentiate from similar browsing tools like 'browse_vault_library' or 'list_recipes'.

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 contexts: offline indexing ('No TouchDesigner connection required') and option to filter by kinds/query. However, it does not explicitly state when not to use or provide alternatives, leaving the agent to infer from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server