Maya MCP

Overview Schema Source Related Servers Discussions Admin

get_scene_info

Retrieve a Maya scene's name, material count, and paginated object list, with name filters and top-level-only options to inspect scene contents.

Instructions

Get the scene name, material count and a page of objects (sorted by name). By default lists top-level objects only and leaves out Maya's default cameras. name_filter takes Maya wildcards, e.g. "spike_*". If "truncated" is true, there are more objects: call again with offset=next_offset. Set top_level_only=false to include objects inside groups. limit is 1-500.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_scene_info"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`name_filter`	No
`top_level_only`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses default exclusions (top-level only, default cameras omitted), the pagination contract (truncated + next_offset), and the limit bound (1-500). It could add a note on read-only/non-destructive nature or performance, but otherwise the behavior is well surfaced.

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?

Front-loads what is returned, then default behavior, then filter, pagination, and scope controls. Every sentence carries actionable information with no filler.

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?

An output schema exists, so return values need not be re-explained, yet the description still clarifies the truncated/next_offset fields that drive pagination. Combined with complete parameter semantics, an agent has everything needed to call and iterate 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?

Schema coverage is 0%, so all meaning comes from the description, and it covers every parameter: limit (1-500), offset (pagination), name_filter (Maya wildcards with example), and top_level_only (false includes grouped objects). This fully compensates for the empty schema descriptions.

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?

States a specific verb (get) and resource (scene info: name, material count, paged objects sorted by name), and implicitly scopes out per-object lookup handled by get_object_info. The default filtering behavior (top-level only, excluding Maya defaults) further distinguishes this aggregate/list tool from siblings like get_object_info or get_selected_objects.

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?

Gives concrete operational guidance: re-call with offset=next_offset when truncated is true, and set top_level_only=false to descend into groups. It does not explicitly name a sibling alternative for drilling into a single object, so it stops short of full when-vs-alternative routing, but the pagination and scope conditions are clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.