Skip to main content
Glama
EYamanS

fmod-studio-mcp

by EYamanS

fmod_ManagedObject_dump

Log all members of a managed object in FMOD Studio by specifying its path or GUID. Use this tool to inspect object properties during live editing.

Instructions

Logs all members. [method · ManagedObject.dump]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesObject to act on: a path (e.g. 'event:/SFX/Hit', 'bank:/Master') or a '{guid}'.
Behavior2/5

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

No annotations provided. Description does not disclose side effects, safety, or output behavior. 'Logs' is vague and could imply console output or internal logging.

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

Conciseness2/5

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

Extremely short but under-specified. The description is concise but lacks necessary detail, crossing into incompleteness.

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?

No output schema and minimal description. Does not explain return format, side effects, or what 'logs all members' produces. Unacceptably incomplete for an agent to use correctly.

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

Parameters3/5

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

Schema coverage is 100% with clear parameter description. However, the tool description adds no additional meaning beyond the schema, so baseline 3.

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 states 'Logs all members' which is a specific verb+resource. It distinguishes from sibling ManagedObject tools (e.g., document, entity) but could be more explicit about what 'members' entails.

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 like fmod_ManagedObject_document or fmod_console_dump. Missing context on prerequisites or scenarios.

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