Skip to main content
Glama

build_object_info_query

Read-onlyIdempotent

Construct a WAAPI object query with filters for path, type, fields, traversal, and name/type constraints. Use this to build queries for retrieving Wwise objects before executing them.

Instructions

Builds a WAAPI ak.wwise.core.object.get query dict from structured parameters. Use this to construct a query before calling execute_waapi_query.

Args: from_path: Root paths to query from. e.g. ["\Containers"] or ["\Events"] from_type: Object types to query from. e.g. ["Sound", "Event", "RandomSequenceContainer"] return_fields: Fields to return per object. Common: "id", "name", "type", "path", "shortId", "parent" select_transform: Traversal direction. One of: "descendants", "ancestors", "children", "parent" where_name_contains: Filter results to objects whose name contains this string. where_type_is: Filter results to specific object types. e.g. ["Sound", "BlendContainer"]

Examples: All descendants of Containers: from_path=["\Containers"], select_transform="descendants"

All Events containing "footstep":
    from_path=["\Events"], select_transform="descendants",
    where_name_contains="footstep", where_type_is=["Event"]

All busses:
    from_path=["\Busses"], select_transform="descendants",
    where_type_is=["Bus", "AuxBus"]

Children of a specific container:
    from_path=["\Containers\Default Work Unit\SFX"],
    select_transform="children"

IMPORTANT — Inherited properties: Properties like @OutputBus return the LOCAL value, not the effective (inherited) value. If @OverrideOutput is false, the object inherits its output bus from an ancestor. To find the actual routing, query the object's ancestors (select_transform="ancestors") and return @OutputBus and @OverrideOutput to find the nearest ancestor that sets the effective bus.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_pathNo
from_typeNo
return_fieldsNo
select_transformNo
where_name_containsNo
where_type_isNo
Behavior5/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds critical behavioral information beyond annotations: it explains that properties like @OutputBus return the local, not effective, inherited value, and how to obtain the effective value by querying ancestors. This is substantial additional context.

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 well-structured with sections: main purpose, Args, Examples, and an Important note. It is front-loaded with the key purpose. However, it is somewhat verbose, containing extensive examples and detailed parameter descriptions, which could be slightly condensed without losing value.

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?

Given the tool's complexity (6 parameters, no output schema, but rich annotations), the description covers the purpose, parameter details, usage context, and an important behavioral nuance (inherited properties). Examples cover typical use cases, making it complete for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

The input schema has 0% description coverage, yet the description provides detailed explanations for all 6 parameters, including types, defaults, and examples. It fully compensates for the schema's lack of descriptions, adding significant meaning.

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 'Builds a WAAPI ak.wwise.core.object.get query dict from structured parameters.' It specifies the verb 'Builds' and the resource 'query dict', and differentiates from siblings like execute_waapi_query by setting up the query to be used with it. Examples further solidify the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use this to construct a query before calling execute_waapi_query,' providing clear usage context. Examples demonstrate common cases. However, it does not explicitly list when not to use it or alternatives, which prevents a perfect score.

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/silver-rain-dev/sk-wwise-mcp'

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