Skip to main content
Glama

get_scene_info

Retrieve comprehensive 3ds Max scene details including file status, object counts, time range, and unit settings to understand the current project state.

Instructions

获取当前 3ds Max 场景的综合信息。

该工具返回当前场景的全面信息,包括文件路径、对象统计、时间范围、 单位设置等,帮助 AI 了解场景的整体状态。

Returns: dict: 操作结果。 - success (bool): 是否成功。 - file_path (str): 当前场景文件的完整路径(未保存时为空)。 - file_name (str): 场景文件名。 - is_saved (bool): 场景是否已保存。 - object_counts (dict): 各类型对象数量统计。 - total (int): 总对象数。 - geometry (int): 几何体数量。 - lights (int): 灯光数量。 - cameras (int): 相机数量。 - helpers (int): 辅助对象数量。 - shapes (int): 样条线数量。 - time_range (dict): 时间/帧范围。 - start (int): 起始帧。 - end (int): 结束帧。 - current (int): 当前帧。 - fps (float): 帧率。 - units (dict): 单位设置。 - system_type (str): 系统单位类型。 - system_scale (float): 系统单位缩放。 - display_type (str): 显示单位类型。 - message (str): 描述信息。

示例调用: get_scene_info()

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the tool as returning comprehensive scene information, which implies a read-only operation without side effects, but does not explicitly state this. It also lacks details on error conditions, performance implications, or authentication needs. The description adds some context about what information is included but misses behavioral traits like whether it requires a loaded scene or works on unsaved files.

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 appropriately sized and front-loaded, starting with the purpose and key details. The detailed return structure is necessary for clarity but could be more concise. The example call at the end is helpful but slightly redundant. Overall, most sentences earn their place, though minor trimming is possible.

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 complexity (providing comprehensive scene data) and lack of annotations or output schema, the description does a good job of explaining what information is returned. It details the return structure extensively, covering file details, object counts, time range, and units. However, it could improve by mentioning behavioral aspects like error handling or prerequisites, but it's largely complete for a read-only informational tool.

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 0 parameters, and the input schema has 100% description coverage (though empty). The description does not need to add parameter semantics, as there are none to document. It correctly omits parameter details, earning a high baseline score for not introducing unnecessary information.

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 tool's purpose: '获取当前 3ds Max 场景的综合信息' (Get comprehensive information about the current 3ds Max scene). It specifies the verb '获取' (get) and the resource '场景的综合信息' (comprehensive scene information), distinguishing it from siblings like get_scene_objects (which lists objects) or get_object_properties (which focuses on specific objects).

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

Usage Guidelines3/5

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

The description implies usage by stating it '帮助 AI 了解场景的整体状态' (helps AI understand the overall state of the scene), suggesting it should be used for general scene assessment. However, it does not explicitly state when to use this tool versus alternatives like get_scene_objects or get_object_properties, nor does it provide exclusions or prerequisites for its use.

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/317431629/3dsMaxMCP'

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