Skip to main content
Glama
sandraschi

vcv-rack-mcp

by sandraschi

vcv_catalog

Search the VCV Rack module catalog, get module details, verify installations, manage library links, and suggest rack configurations for patch building.

Instructions

Module catalog portmanteau — search, get_module, verify_installed, library_link, sideload, suggest_rack.

Return Format

{"success": bool, "operation": str, ...operation-specific keys}

Examples

vcv_catalog(operation="search", function_tag="osc") vcv_catalog(operation="get_module", plugin_slug="Fundamental", model_slug="VCO") vcv_catalog(operation="suggest_rack", persona_tag="generative", intent="ambient drone")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
limitNo
queryNo
intentNo
operationYes
model_slugNo
persona_tagNo
plugin_slugNo
function_tagNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations provided, and the description does not disclose behavioral traits such as mutability, side effects, or required permissions. Operations like 'sideload' may have destructive effects, but this is not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and includes a return format and examples, which are helpful. However, the opening phrase 'Module catalog portmanteau' is unconventional and unclear. It is concise but sacrifices clarity.

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

Completeness1/5

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

Given the tool's complexity (9 parameters, multiple operations), the description lacks essential details. Without parameter documentation or behavioral cues, an agent cannot reliably use all features correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain parameter meanings beyond example usage. Parameters like 'function_tag', 'plugin_slug', etc., are used in examples but not defined.

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 lists multiple operations (search, get_module, etc.) indicating a multi-purpose catalog tool. It distinguishes from siblings like hub_status or show_catalog_card, which are more specific. However, the term 'portmanteau' is vague and the operations are not defined individually.

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 explicit guidance on when to use this tool versus siblings. Examples show usage patterns but do not clarify when to choose one operation over another or when to use vcv_catalog vs other tools.

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/sandraschi/vcv-rack-mcp'

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