Skip to main content
Glama
truman-t3

KeyShot MCP

by truman-t3
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Set a KeyShot camera

keyshot_set_camera
Destructive

Set or update a named camera in a KeyShot scene by specifying position, target, distance, field of view, or focal length, then save the edited scene.

Instructions

Create or update a named camera using position, target, distance, field of view, or focal length, then save the edited scene.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
upNoOptional camera up direction [x, y, z]. Requires position and lookAt.
lookAtNoCamera target [x, y, z]. Must be provided together with position.
distanceNoPositive KeyShot camera distance.
positionNoCamera position [x, y, z]. Must be provided together with lookAt.
scenePathYesAbsolute path to an existing KeyShot scene file to open. Input files may be outside the configured output directory.
cameraNameNoSaved camera to update, or the name to use when creating a camera.
fieldOfViewNoField of view in degrees, greater than 0 and less than 180. Cannot be combined with focalLength.
focalLengthNoFocal length from 5 to 200 mm. Cannot be combined with fieldOfView.
outputScenePathYesDestination path for the saved KeyShot scene. The path must stay inside KEYSHOT_OUTPUT_DIR unless external outputs are explicitly enabled.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when the requested operation completed successfully.
dataNoOperation-specific structured result data, or null when unavailable.
errorYesHuman-readable failure reason, or null after success.
warningsYesNon-fatal conditions the user or agent should review.
errorCodeNoStable error category for common failures.
outputFilesYesAbsolute paths of images or scene files created by the operation.
suggestionsNoActionable recovery steps for the user or agent.
keyshotStdoutTailYesTruncated tail of KeyShot headless output for diagnostics.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed21 schema fields changedv0.10.0
    • addedInput schema / properties / cameraName / description
      Added value: +"Saved camera to update, or the name to use when creating a camera."
    • addedInput schema / properties / distance / description
      Added value: +"Positive KeyShot camera distance."
    • addedInput schema / properties / fieldOfView
      Added value: +{
+  "description": "Field of view in degrees, greater than 0 and less than 180. Cannot be combined with focalLength.",
+  "exclusiveMaximum": 180,
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / focalLength
      Added value: +{
+  "description": "Focal length from 5 to 200 mm. Cannot be combined with fieldOfView.",
+  "maximum": 200,
+  "minimum": 5,
+  "type": "number"
+}
    • removedInput schema / properties / lookAt / $ref
      Removed value: -"#/properties/position"
    • addedInput schema / properties / lookAt / description
      Added value: +"Camera target [x, y, z]. Must be provided together with position."
    • addedInput schema / properties / lookAt / items
      Added value: +[
+  {
+    "$ref": "#/properties/position/items/0"
+  },
+  {
+    "$ref": "#/properties/position/items/1"
+  },
+  {
+    "$ref": "#/properties/position/items/2"
+  }
+]
    • addedInput schema / properties / lookAt / maxItems
      Added value: +3
    • addedInput schema / properties / lookAt / minItems
      Added value: +3
    • addedInput schema / properties / lookAt / type
      Added value: +"array"
    • addedInput schema / properties / outputScenePath / description
      Added value: +"Destination path for the saved KeyShot scene. The path must stay inside KEYSHOT_OUTPUT_DIR unless external outputs are explicitly enabled."
    • addedInput schema / properties / position / description
      Added value: +"Camera position [x, y, z]. Must be provided together with lookAt."
    • addedInput schema / properties / scenePath / description
      Added value: +"Absolute path to an existing KeyShot scene file to open. Input files may be outside the configured output directory."
    • removedInput schema / properties / up / $ref
      Removed value: -"#/properties/position"
    • addedInput schema / properties / up / description
      Added value: +"Optional camera up direction [x, y, z]. Requires position and lookAt."
    • addedInput schema / properties / up / items
      Added value: +[
+  {
+    "$ref": "#/properties/position/items/0"
+  },
+  {
+    "$ref": "#/properties/position/items/1"
+  },
+  {
+    "$ref": "#/properties/position/items/2"
+  }
+]
    • addedInput schema / properties / up / maxItems
      Added value: +3
    • addedInput schema / properties / up / minItems
      Added value: +3
    • addedInput schema / properties / up / type
      Added value: +"array"
    • changedInput schema / required
      Previous value: -[
-  "scenePath",
-  "position",
-  "lookAt",
-  "outputScenePath"
-]New value: +[
+  "scenePath",
+  "outputScenePath"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Operation-specific structured result data, or null when unavailable."
+    },
+    "error": {
+      "description": "Human-readable failure reason, or null after success.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "errorCode": {
+      "description": "Stable error category for common failures.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "keyshotStdoutTail": {
+      "description": "Truncated tail of KeyShot headless output for diagnostics.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "True when the requested operation completed successfully.",
+      "type": "boolean"
+    },
+    "outputFiles": {
+      "description": "Absolute paths of images or scene files created by the operation.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "suggestions": {
+      "description": "Actionable recovery steps for the user or agent.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "warnings": {
+      "description": "Non-fatal conditions the user or agent should review.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ok",
+    "outputFiles",
+    "warnings",
+    "keyshotStdoutTail",
+    "error"
+  ],
+  "type": "object"
+}
  2. First observedv0.2.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnly=false, and the description aligns by stating 'create or update' and 'save the edited scene.' However, it does not disclose additional behavioral details like whether an existing scene is overwritten or if any permissions/validations apply, so it only minimally adds transparency beyond the annotations.

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?

The description is a single, well-structured sentence with the action verb front-loaded. It avoids filler and directly states the purpose, making it highly concise and readable.

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 detailed schema with 100% parameter coverage and the presence of an output schema, the description sufficiently covers the primary action. Minor gaps exist around usage versus camera-preset tools, but the high-quality schema information compensates, making the description adequately complete.

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?

The schema description coverage is 100% with per-property explanations, including constraints like position/lookAt pairing and fieldOfView/focalLength exclusion. The description merely lists the parameter categories and does not add meaningful semantics beyond what the schema already provides, so a baseline score of 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 uses a specific verb--create or update--and identifies the resource as a named camera, with the adjustable parameters listed. It clearly distinguishes itself from sibling tools like keyshot_list_cameras or keyshot_apply_camera_preset by emphasizing direct camera configuration and scene saving.

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

Usage Guidelines4/5

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

The description clearly implies the tool is for directly configuring a camera and saving the result, but it does not explicitly address when to use it instead of alternatives such as applying a camera preset. The absence of explicit exclusions keeps it from a perfect score, though the context is unambiguous.

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/truman-t3/keyshot-mcp'

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