Skip to main content
Glama
truman-t3

KeyShot MCP

by truman-t3

keyshot_apply_material_preset

Apply a material preset from the library to a scene object and save the updated scene.

Instructions

Apply a named material preset (from the preset library) to a scene object and save the resulting scene.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scenePathYes
objectNameNo
objectPathNo
presetNameYes
outputScenePathYes
Behavior2/5

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

The description only says it applies and saves. It does not disclose what happens to the original scene, whether the output file is overwritten, or any permission requirements. Without annotations, the agent has little insight into side effects.

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 description is a single sentence, which is concise but lacks structure. It front-loads the action but omits parameter explanations, making it less helpful than it could be. Every sentence earns its place, but missing information reduces effectiveness.

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?

Given 5 parameters and no output schema or annotations, the description is insufficient. It does not cover how to identify the object, what the output scene path implies, or any return information. The description underperforms relative to the tool's complexity.

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 coverage is 0%, so the description should explain parameters. It mentions presetName and outputScenePath implicitly, but the crucial parameters objectName and objectPath are not described. The agent doesn't know how to identify the target object or the distinction between the two.

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 clearly states the tool applies a named material preset from the preset library to a scene object and saves the scene. It uses specific verbs and distinguishes from sibling tools like keyshot_apply_material by specifying 'preset library' and the saving action.

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?

No usage guidelines are provided. The description does not give when to use this tool versus alternatives like keyshot_apply_material or keyshot_list_material_presets. There is no context on prerequisites or exclusions.

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