Skip to main content
Glama

focus_camera_on_object

Point a camera at a chosen object so it stays framed for rendering or visual verification. Use it to aim any scene camera at a target object by name.

Instructions

Point/focus a camera at an object.

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": {
      "camera": "<camera>",
      "object_name": "<object_name>"
    },
    "name": "focus_camera_on_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
cameraYes
object_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and discloses almost nothing. It doesn't say whether this mutates camera rotation/location, whether it adds a tracking constraint, whether the change is reversible, or what side effects arise, and the slash between "point" and "focus" leaves the actual operation ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, so there's nothing to trim. However, its brevity reflects under-specification rather than efficiency, given two undocumented required parameters and no explanation of behavior.

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

Completeness2/5

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

The output schema exists, so return values don't need explaining. Even so, for a two-parameter mutation with 0% schema coverage and no annotations, the definition leaves critical details uncovered: what gets changed on the camera and what preconditions must hold.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain both parameters and it doesn't. It hints that one input is a camera and the other an object name, but never states the expected identifier format, whether the camera is referenced by name or datablock, or what counts as a valid object_name.

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 gives a concrete verb+resource ("Point/focus a camera at an object"), which is far more specific than the name alone. It doesn't differentiate from neighbors such as camera_view, set_active_camera, or configure_camera_lens, so the agent can't tell which aim/focus operation is the right one.

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?

There is no when-to-use guidance, no prerequisite (must the camera exist or be active?), and no mention of an alternative tool for aiming or optics. The agent must infer usage entirely from a single sentence.

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