Skip to main content
Glama

ping

Verifies connectivity to FMOD Studio and returns the installed version number, ensuring the audio integration is operational.

Instructions

Sanity-check the FMOD Studio connection. Returns version if available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation: sends JavaScript to FMOD Studio via TCP to retrieve the studio version. Wraps the version lookup in try/catch for resilience, returns {ok, version} dict.
    async def ping(client: StudioClient) -> dict[str, Any]:
        """Sanity-check the TCP connection and fetch Studio version if available."""
        js = """
            var v = null;
            try { v = studio.version; } catch (e) {}
            try { if (v == null && studio.application && studio.application.version) v = studio.application.version; } catch (e) {}
            return { ok: true, version: v };
        """
        return await client.eval(js)
  • Tool registration via @mcp.tool() decorator on FastMCP instance. Delegates to discovery.ping() with a lazily-initialized StudioClient singleton.
    @mcp.tool()
    async def ping() -> dict[str, Any]:
        """Sanity-check the FMOD Studio connection. Returns version if available."""
        return await discovery.ping(_studio())
  • The StudioClient.eval() method is called by discovery.ping() to send/receive JS over TCP. Wraps the snippet in a sentinel-tagged IIFE for response framing.
    async def eval(self, js: str, timeout: float = 30.0) -> Any:
        """Evaluate a JavaScript snippet in Studio and return the parsed value.
    
        The caller is responsible for making sure ``js`` uses ``return`` to
        surface its value (the snippet is wrapped in an IIFE).
        """
        req_id = uuid.uuid4().hex
        # Substitute the request id into the template BEFORE injecting user JS,
        # so a snippet that happens to contain "__ID__" or "__JS__" cannot
        # corrupt the surrounding wrapper.
        wrapped = _WRAPPER_TEMPLATE.replace("__ID__", req_id).replace("__JS__", js)
        # Studio's terminal evaluates per-line: strip `//` comments and collapse
        # internal newlines so the whole command arrives as one line.
        wrapped = _flatten_js(wrapped)
        async with self._lock:
            # connect() inside the lock so concurrent callers don't open
            # multiple sockets or fight over the same StreamReader.
            await self.connect()
            self._log_command(req_id, js)
            assert self._writer is not None
            self._writer.write(wrapped.encode("utf-8"))
            await self._writer.drain()
            return await self._await_response(req_id, timeout)
  • Module docstring lists ping as a read-only discovery tool. No explicit schema beyond the return type hint dict[str, Any].
    """Read-only tools: ping, list_banks, list_events, list_buses, get_event."""
    from __future__ import annotations
  • The StudioClient class that manages the TCP connection to FMOD Studio and is used by discovery.ping().
    class StudioClient:
        """Single-connection, serialized TCP client for FMOD Studio scripting."""
    
        def __init__(
            self,
            host: str = DEFAULT_HOST,
            port: int = DEFAULT_PORT,
            log_path: Path | None = None,
        ) -> None:
            self.host = host
            self.port = port
            self._reader: asyncio.StreamReader | None = None
            self._writer: asyncio.StreamWriter | None = None
            self._lock = asyncio.Lock()
            self._buffer = ""
            self._log_path = log_path or (Path.home() / ".cache" / "fmod-mcp" / "commands.log")
            self._log_path.parent.mkdir(parents=True, exist_ok=True)
    
        async def connect(self) -> None:
            if self._writer is not None:
                return
            try:
                self._reader, self._writer = await asyncio.open_connection(self.host, self.port)
            except OSError as exc:
                raise ConnectionError(
                    f"Could not reach FMOD Studio at {self.host}:{self.port} — "
                    "is Studio running with the project open and TCP scripting enabled?"
                ) from exc
            await self._drain_banner()
    
        async def _drain_banner(self) -> None:
            """Studio prints a prompt/banner on connect; swallow it briefly."""
            assert self._reader is not None
            try:
                while True:
                    chunk = await asyncio.wait_for(self._reader.read(4096), timeout=0.2)
                    if not chunk:
                        break
            except asyncio.TimeoutError:
                pass
    
        async def close(self) -> None:
            if self._writer is None:
                return
            self._writer.close()
            try:
                await self._writer.wait_closed()
            except Exception:  # noqa: BLE001 — best-effort cleanup
                pass
            self._reader = None
            self._writer = None
            self._buffer = ""
    
        async def eval(self, js: str, timeout: float = 30.0) -> Any:
            """Evaluate a JavaScript snippet in Studio and return the parsed value.
    
            The caller is responsible for making sure ``js`` uses ``return`` to
            surface its value (the snippet is wrapped in an IIFE).
            """
            req_id = uuid.uuid4().hex
            # Substitute the request id into the template BEFORE injecting user JS,
            # so a snippet that happens to contain "__ID__" or "__JS__" cannot
            # corrupt the surrounding wrapper.
            wrapped = _WRAPPER_TEMPLATE.replace("__ID__", req_id).replace("__JS__", js)
            # Studio's terminal evaluates per-line: strip `//` comments and collapse
            # internal newlines so the whole command arrives as one line.
            wrapped = _flatten_js(wrapped)
            async with self._lock:
                # connect() inside the lock so concurrent callers don't open
                # multiple sockets or fight over the same StreamReader.
                await self.connect()
                self._log_command(req_id, js)
                assert self._writer is not None
                self._writer.write(wrapped.encode("utf-8"))
                await self._writer.drain()
                return await self._await_response(req_id, timeout)
    
        async def _await_response(self, req_id: str, timeout: float) -> Any:
            assert self._reader is not None
            loop = asyncio.get_event_loop()
            deadline = loop.time() + timeout
            while True:
                found = self._consume_response(req_id)
                if found is not None:
                    kind, payload = found
                    if kind == "OK":
                        return payload
                    message = payload.get("message", "FMOD Studio error") if isinstance(payload, dict) else str(payload)
                    stack = payload.get("stack", "") if isinstance(payload, dict) else ""
                    raise StudioError(f"{message}\n{stack}".rstrip())
                remaining = deadline - loop.time()
                if remaining <= 0:
                    raise TimeoutError(
                        f"FMOD Studio did not respond to request {req_id} within {timeout}s"
                    )
                try:
                    chunk = await asyncio.wait_for(self._reader.read(4096), timeout=remaining)
                except asyncio.TimeoutError as exc:
                    raise TimeoutError(
                        f"FMOD Studio did not respond to request {req_id} within {timeout}s"
                    ) from exc
                if not chunk:
                    raise ConnectionError("FMOD Studio closed the TCP connection")
                self._buffer += chunk.decode("utf-8", errors="replace")
    
        def _consume_response(self, req_id: str) -> tuple[str, Any] | None:
            for kind, sentinel in (("OK", _SENTINEL_OK), ("ERR", _SENTINEL_ERR)):
                tag = f"{sentinel}:{req_id}:"
                idx = self._buffer.find(tag)
                if idx == -1:
                    continue
                end = self._buffer.find("\n", idx + len(tag))
                if end == -1:
                    return None
                payload_str = self._buffer[idx + len(tag) : end]
                self._buffer = self._buffer[end + 1 :]
                try:
                    return kind, json.loads(payload_str)
                except json.JSONDecodeError as exc:
                    raise StudioError(f"Malformed JSON from Studio: {payload_str!r}") from exc
            return None
    
        def _log_command(self, req_id: str, js: str) -> None:
            try:
                with self._log_path.open("a", encoding="utf-8") as fh:
                    fh.write(f"# {req_id}\n{js.rstrip()}\n\n")
            except OSError as exc:
                logger.warning("Could not write to command log %s: %s", self._log_path, exc)
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It states the tool is a sanity check and returns version, but does not mention side effects, error cases, or any constraints. Given the tool's simplicity, some might consider this sufficient, but for a strict scoring, it lacks detail.

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?

The description is extremely concise with only two sentences. It is front-loaded with the primary action and result. Every word adds value, and there is no unnecessary information.

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

Completeness4/5

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

Given the tool's simplicity and the presence of an output schema (which handles return structure), the description is adequately complete. It tells the agent what to expect (connection check and version). minor gap: lack of error behavior, but for a ping tool this is acceptable.

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 has zero parameters, so per the rubric the baseline is 4. The description does not need to add parameter information. The schema coverage is 100%, and the description does not repeat what is already in the schema.

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 clearly states the tool's purpose: checking the FMOD Studio connection and returning version info. It uses a specific verb ('sanity-check') and resource ('FMOD Studio connection'), which distinguishes it from sibling tools like list_banks or create_event. However, the description could be more explicit about the return value format.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or scenarios where ping is appropriate. The description does not help the agent decide if this is the right tool.

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