Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

asset_plan

Freezes an asset revision, role, toolchain, and transfer budget for planning without downloading models or starting physics; unknown constraints block preparation.

Instructions

Freeze a selected revision, role, toolchain and transfer budget without downloading models or starting physics. Unknown constraints block preparation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset_ref": "<asset_ref>"
    },
    "name": "asset_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_refYes
parametersNo
profile_idNovisual_prop_v1
budget_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: no model download, no physics/simulation start, and a blocking failure mode on unknown constraints - effectively a side-effect-light planning operation. It stops short of saying whether anything is persisted, whether the freeze is reversible, or what permissions are required.

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

Conciseness4/5

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

Two compact, front-loaded sentences with no filler; the constraint-blocking clause earns its place. The density of jargon ('freeze', 'role', 'toolchain') means the brevity costs some comprehensibility, but nothing is redundant.

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

Completeness3/5

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

For a 4-parameter tool with a nested untyped object, no annotations, and no output schema, the description covers the safety/behavioral profile reasonably but leaves the return value and the meaning of the nested asset_ref/parameters structures unaddressed. An agent could invoke it, but with notable uncertainty about inputs and outcome.

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?

Schema description coverage is 0% across 4 parameters, so the description must compensate. It partially does: 'transfer budget' maps to budget_bytes and 'selected revision' plausibly maps to asset_ref, with 'role and toolchain' presumably living in the untyped parameters object. But the mapping is loose and the opaque nested object and profile_id default are not explained, leaving real ambiguity.

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?

States a specific action ('freeze a selected revision, role, toolchain and transfer budget') on a specific resource, and delimits it against neighboring capabilities by saying it happens 'without downloading models or starting physics,' implicitly separating it from acquire/prepare tools. The verb 'freeze' is domain jargon and slightly opaque about what is actually persisted, which keeps it from a 5.

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

Usage Guidelines3/5

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

The 'without downloading models or starting physics' clause implies this is the planning/gating step before asset_acquire or asset_prepare, and 'Unknown constraints block preparation' hints at a validation gate. However, no alternative tool is named and no explicit when-to-use/when-not-to-use rule is stated, so the agent must infer the sequencing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.