Skip to main content
Glama
Sign In
sfx

sfx

by gteuscher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sfx_list_presets

Browse available sound-effect presets, each with a one-line summary, to quickly choose a starting point for your synthesis.

Instructions

List available presets with a one-line summary of each.

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": "sfx_list_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are present, so the description must carry the safety signal. 'List' is clearly read-only, and 'available presets with a one-line summary' tells the agent what output to expect. It doesn't state 'no side effects' explicitly, but the verb makes that unambiguous for this tool type.

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?

Single sentence, imperative verb, focus on output detail. Nothing wasted.

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 zero-parameter read-only listing with an output schema present, no further information is needed to invoke 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?

The tool takes zero parameters foreseeable from context and the input schema; baseline 4 applies. The description adds no requirements but none are needed.

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 the exact action ('List available presets') and specifies the output detail ('one-line summary of each'). This clearly differentiates it from sibling tools like sfx_save_preset or sfx_render_preset.

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 when to use it (whenever an agent needs to see what presets exist), but does not explicitly state when to prefer it over siblings or call it before save/render operations. Reasonable but no exclusions or alternatives named.

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