Set the Isaac Sim viewport camera position and target point to aim the view at a specific coordinate for inspection.
Point the viewport camera, e.g. eye=[1.2, 1.2, 1.0] target=[0, 0, 0.3].
| Name | Required | Description | Default |
|---|---|---|---|
| eye | Yes | ||
| target | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: not whether this mutates persistent scene state or is a transient viewport-only change, not whether coordinates are world-space or robot-base-relative, and not whether a render must occur afterward. For a camera-control tool with zero annotation coverage this is a substantial gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence that states the action and immediately grounds it with a concrete example. Nothing is padded or repeated from the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 described, and with only two required numeric-vector params the surface is small. However, missing coordinate-frame conventions and persistence semantics leave an agent guessing about how the values will be interpreted.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% — the schema gives only titles ('Eye', 'Target') with no semantic text. The example (eye=[1.2, 1.2, 1.0], target=[0, 0, 0.3]) does imply 3-element numeric vectors and that 'eye' is the camera position while 'target' is the look-at point, which partially compensates, but the coordinate frame and units are never stated.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('point') and resource ('viewport camera'), which cleanly separates it from siblings like sim_set_pose and sim_set_targets that manipulate robot/object targets rather than the viewport. It does not explicitly call out that distinction, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool, when not to, or which sibling to prefer (e.g., sim_screenshot or sim_set_pose). The inline example hints at typical values but conveys no usage conditions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.