Skip to main content
Glama

set_event_property

Assign a value to a scalar property (like volume or pitch) on a specified FMOD event by providing the event path, property name, and value.

Instructions

Set a scalar property on an event (volume, pitch, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_pathYes
property_nameYes
valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler that builds a JavaScript snippet to look up the event, set a property by name, and return the result via StudioClient.eval().
    async def set_event_property(
        client: StudioClient,
        event_path: str,
        property_name: str,
        value: Any,
    ) -> dict[str, Any]:
        """Set a property on an event (volume, pitch, min/max distance, etc.)."""
        js = f"""
            var evt = studio.project.lookup({json.dumps(event_path)});
            if (!evt) throw new Error("Event not found: " + {json.dumps(event_path)});
            evt[{json.dumps(property_name)}] = {json.dumps(value)};
            return {{ ok: true, path: evt.getPath(), property: {json.dumps(property_name)}, value: evt[{json.dumps(property_name)}] }};
        """
        return await client.eval(js)
  • Registers the tool with FastMCP via @mcp.tool() decorator and delegates to events.set_event_property.
    @mcp.tool()
    async def set_event_property(
        event_path: str,
        property_name: str,
        value: Any,
    ) -> dict[str, Any]:
        """Set a scalar property on an event (volume, pitch, etc.)."""
        return await events.set_event_property(_studio(), event_path, property_name, value)
  • Test verifying that set_event_property correctly serializes the property name and value into the JavaScript sent to FMOD Studio.
    async def test_set_event_property_serializes_value(
        client: StudioClient, mock_studio: MockStudio
    ):
        mock_studio.responder = responder_sequence([("OK", {"ok": True})])
        await events.set_event_property(client, "event:/a", "volume", -3.0)
        js = _last_sent_js(mock_studio)
        assert '"volume"' in js
        assert "-3.0" in js
Behavior2/5

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

No annotations provided; the description only states 'set a scalar property' but omits behavioral details such as whether the operation is reversible, auth requirements, or side effects on other properties.

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 efficient sentence, but could be more informative without sacrificing conciseness.

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?

Despite an output schema being present, the description does not explain return values or constraints. The 3 required parameters lack detail on valid ranges or formats for the scalar value.

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?

The input schema has 3 parameters with 0% description coverage. The description only loosely explains 'scalar property' and examples, not adding meaning for 'event_path' or 'value' format.

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 action ('set'), the resource ('event property'), and provides examples ('volume, pitch'), distinguishing it from sibling tools like 'set_effect_param' or 'add_effect'.

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 guidance on when to use this tool versus alternatives (e.g., when to use set_effect_param instead). The description does not specify prerequisites or conditions.

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

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