Skip to main content
Glama
EYamanS

fmod-studio-mcp

by EYamanS

fmod_create_event

Create an event in FMOD Studio, import an audio file as a one-shot, and assign to a bank in a single composite operation.

Instructions

Composite: create an event, optionally import a one-shot sound onto a new audio track and assign the event to a bank. Equivalent to a create + importAudioFile + addGroupTrack + addSound + set audioFile + add bank relationship.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
soundNoAbsolute path to an audio file to place as a one-shot.
bank_nameNoBank to assign to, e.g. 'Master'. Omit to skip.
folder_pathNoExisting folder lookup path, e.g. 'event:/SFX'.
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the composite nature but lacks details on side effects, error handling, atomicity, or return value.

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 one front-loaded sentence listing the composite steps, efficiently conveying the essence without unnecessary words.

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

Completeness2/5

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

Given four parameters and no output schema or annotations, the description lacks preconditions (e.g., folder existence), postconditions, and order of operations, making it incomplete for confident use.

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

Parameters2/5

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

Schema coverage is 75% and the description adds no extra meaning beyond what the schema already provides for 'sound', 'bank_name', and 'folder_path'. The 'name' parameter is undocumented in both schema and description.

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?

The description clearly states the tool creates an event and optionally imports a sound and assigns a bank. It explicitly lists equivalent sub-tools, distinguishing it from the many individual sibling tools.

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 usage is implied by stating it's a composite of several steps, but no explicit guidance on when to use this vs alternatives, nor when not to use it.

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/EYamanS/fmod-studio-mcp'

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