Skip to main content
Glama
full-aigc-plugins

partme_blender

by full-aigc-plugins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

simulation.quick_smoke

blender_simulation_quick_smoke

Run a quick smoke simulation on specified flows with configurable frame range and resolution to preview or validate fluid behavior before committing to a full bake.

Instructions

PartMe Blender Harness command simulation.quick_smoke. Risk: standard; maturity: L3. Requirements: Per-request argument checks and session policy still apply

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowsYes
frameEndNo
_requestIdNoStable request id for replay safety
frameStartNo
resolutionNo
_authorizationNoAction-bound Harness authorization claim
_transactionIdYesHarness milestone transaction id
_expectedSceneRevisionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • removedInput schema / properties / resolution / description
      Removed value: -"Official uploader resolution label; default 720p"
    • addedInput schema / properties / resolution / minimum
      Added value: +1
    • changedInput schema / properties / resolution / type
      Previous value: -"string"New value: +"integer"
  2. First observedv0.1.0

TDQS

D1.1/5.0
Behavior1/5

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

Annotations already indicate non-read-only, non-idempotent, and non-destructive behavior. The description adds no behavioral detail—no side effects, scene modifications, or prerequisites—beyond what annotations already provide, and it does not contradict them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is extremely short, but this is under-specification rather than conciseness. It contains no functional substance, and the minimal content is not front-loaded with useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex simulation tool with 8 parameters, an output schema, and many simulation siblings, the description is completely inadequate. It omits purpose, usage, parameter meanings, and expected outcomes, making it impossible for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 38% description coverage, with only _requestId and _authorization described. The description does not explain any parameter, including required flows or optional frameStart/frameEnd/resolution, leaving agents without guidance on how to populate them.

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

Purpose1/5

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

The description only names the command and provides metadata (risk, maturity, requirements) but never states what the tool does. It does not mention smoke simulation, quick testing, or any action it performs, making it essentially a tautology of the tool name.

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

Usage Guidelines1/5

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

No guidance is given on when to use this tool versus alternatives like blender_simulation_cloth or blender_simulation_rigid_body. There is no context about typical scenarios, exclusions, or comparisons to 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