Skip to main content
Glama

frame_objects

Frames objects in a camera view to position and verify them for rendering or inspection.

Instructions

Frame objects in a camera view.

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": "frame_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
cameraNo
object_namesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. It does not say whether it mutates the camera transform, requires an active camera, what happens if object_names is omitted (which is allowed since 0 required params), or whether the change is undoable.

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 filler, but it is under-specified rather than concise. There is no structure to indicate scope, defaults, or the effect of the operation.

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?

An output schema exists, so return values need not be explained, but for a zero-required-parameter mutation-style tool the description leaves the essential behavior unspecified. An agent cannot confidently decide between calling this, camera_view, or capture_camera_view.

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% for both parameters, so the description must compensate and largely fails. 'camera view' loosely hints at the camera parameter and 'objects' at object_names, but it does not explain identifier formats, null/default behavior, or the interaction between the two (e.g. framing a subset vs. everything).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Frame' and resource 'objects in a camera view' give a rough idea, but 'frame' is ambiguous in 3D tooling (fit viewport? position the camera to encompass objects? render?). It does not distinguish itself from siblings like camera_view, capture_camera_view, or get_current_frame.

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 or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as camera_view or capture_camera_view. The agent must guess how this differs from the many other camera-related siblings.

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