Skip to main content
Glama
whatanaiceguy

kuruitsugizaki

by whatanaiceguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

presets

Read-onlyIdempotent

List plugin sound IDs in catalog order, optionally filtered by words. Pick an instrument or effect sound for project_write after checking plugin names.

Instructions

List the presets that load by name for one plugin, as ids in catalog order; an id goes into project_write as an instrument's or effect's preset. Call it after plugins, when choosing a sound. Returns {plugin, kind, total, presets}; total counts every match even when limit cuts the list. A plugin name that matches nothing or several plugins returns {ok: false, error} naming the candidates. Reads files only; FL need not run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoat most this many ids
queryNowords that must all appear in the id, case-insensitive, any order, e.g. 'bass reese'
pluginYesthe plugin's name as plugins lists it; a unique part of it works

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.1
    • addedInput schema / properties / limit / description
      Added value: +"at most this many ids"
    • addedInput schema / properties / plugin / description
      Added value: +"the plugin's name as plugins lists it; a unique part of it works"
    • addedInput schema / properties / query / description
      Added value: +"words that must all appear in the id, case-insensitive, any order, e.g. 'bass reese'"
  2. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the return shape ({plugin, kind, total, presets}), that total counts every match even when limit truncates the list, the ambiguous-match error behavior ({ok: false, error} naming candidates), and that it only reads files (FL need not run). This is rich context that annotations alone would not convey.

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 dense and front-loads purpose, then workflow, then return/error behavior. Every sentence carries information, though the single run-on style is slightly heavy; nothing is redundant.

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?

With no output schema, the description fully compensates by describing the return shape, the total/limit relationship, and the error case. Combined with 100% parameter coverage, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds meaning: 'catalog order' ordering and the fact that total counts all matches even when limit cuts the list, which clarifies the limit parameter's semantics. The plugin matching behavior (unique part, ambiguous -> error) is also elaborated.

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?

States a specific verb (List) and resource (presets) scoped to one plugin, and clarifies that ids are returned in catalog order. An agent can distinguish it from siblings like plugins and params without opening the schema.

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?

Explicit sequencing guidance: 'Call it after plugins, when choosing a sound.' It also routes the output forward, noting an id 'goes into project_write as an instrument's or effect's preset,' which tells the agent how this tool fits the workflow.

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