Skip to main content
Glama
Sign In
mcp-for-maya

mcp-for-maya

by Xxx91n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Camera Orbit

camera_orbit

Create an animated turntable camera that orbits a specified point in Maya, generating motion curves for rendering or reviewing a scene from all angles.

Instructions

Create an orbiting camera with turntable animation around a point.

Side effects: creates a new camera and animation curves in the scene and marks the scene dirty. Not idempotent — each call adds another camera. Requires an active Maya session.

Boundary: Disambiguated from camera_create (static shot-type framing; use camera_orbit only when an animated orbit is needed).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "center": "<center>"
    },
    "name": "camera_orbit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCamera name.CAM_orbit
centerYesOrbit center as a JSON string "[x, y, z]".
framesNoNumber of frames for one full orbit.
radiusNoOrbit radius in scene units.
session_keyNoMaya session key.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • changedInput schema / properties / center / description
      Previous value: -"JSON string with center position [x, y, z]."New value: +"Orbit center as a JSON string \"[x, y, z]\"."
    • changedInput schema / properties / frames / description
      Previous value: -"Number of frames for full orbit."New value: +"Number of frames for one full orbit."
  2. First observedv0.4.1

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false, but the description adds substantial context beyond them: it specifies that a camera and animation curves are created, that the scene is marked dirty, that each call adds another camera, and that an active Maya session is required. This is exactly the kind of operational side-effect detail annotations cannot convey.

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?

It is three short, front-loaded paragraphs: purpose first, then side effects, then boundary. Every sentence carries distinct decision-relevant information with no repetition or 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?

With annotations covering the safety profile, a full input schema, and an output schema handling return values, the description supplies the remaining decision-critical facts: side effects, non-idempotence, session requirement, and sibling disambiguation. Nothing needed to call the tool correctly is missing.

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 description coverage is 100%, so the schema already documents every parameter including center, frames, radius, name, and session_key. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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 states a specific verb and resource: 'Create an orbiting camera with turntable animation around a point.' It also distinguishes the tool from its sibling camera_create by defining the boundary condition (static framing vs animated orbit), so an agent can choose correctly without opening either schema.

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

Usage Guidelines5/5

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

It explicitly names the alternative (camera_create) and the condition that selects this tool: use camera_orbit only when an animated orbit is needed. This is direct when/when-not guidance with a sibling named.

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

Deploy Server

Other Tools