View editable common baking parameters and, optionally, a specific baker's typed property metadata for a texture set to verify and adjust bake settings.
Inspect editable common parameters and one baker's typed property metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| baker | No | ||
| texture_set | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a read-only inspection, but does not state whether it mutates anything, what permissions are needed, or how the editable versus non-editable parameters behave. It also does not clarify the interaction with the required texture_set parameter.
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?
The description is a single efficient sentence with no wasted words, but it is under-specified rather than genuinely concise. It front-loads the action but does not provide enough substance for the tool's complexity.
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 explained. However, with two parameters at 0% schema coverage and no annotations, the description leaves too much unspecified, including parameter meanings, read-only behavior, and when this inspection is appropriate.
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%, so the description must compensate. It only loosely maps 'one baker's' to the optional baker parameter and does not explain the required texture_set parameter, acceptable formats, or what 'typed property metadata' means in practice.
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 states a specific verb, 'inspect,' and identifies the resource area: editable common parameters and one baker's typed property metadata. However, 'common parameters' is vague, and it does not distinguish itself from the sibling tool 'inspect_baking' or explain what inspecting yields beyond metadata.
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 explicit guidance on when to use this tool versus alternatives such as 'inspect_baking' or 'configure_baking.' The only implied context is inspection of baking parameters, but no exclusions or selection criteria are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.