Skip to main content
Glama

apply_force

Pushes a rigid body through PhysX using a force or impulse, so mass affects motion. Use it to move robots or objects in a running or paused simulation.

Instructions

Push a rigid body through PhysX with a force or an impulse, so its mass counts. The simulation must be playing or paused. A push on an articulation's link, such as a robot's, moves the robot through its joints: a floating robot touching nothing changes speed by the impulse over its whole mass; a fixed robot's link turns about its joints, and on the ground friction takes some of the push. The answer gives the point pushed at and the path the push took: method: physx, PhysX's own push, or method: tensor. With /physics/suppressReadback on, as Isaac Sim's GPU device sets it for PhysX's Direct GPU API, the push goes through PhysX's tensor API. Under that API a second push on a body before the next physics step replaces the first, so push once per body per step, combining pushes into one; pushes on different bodies each land. Refused for a prim without RigidBodyAPI, a disabled or kinematic body, and one a fixed joint holds to the world (a fixed robot's base). To place a body rather than push it, use set_prim_transform.

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": {
      "prim_path": "<prim_path>",
      "force": "<force>"
    },
    "name": "apply_force"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceYes[fx, fy, fz]: an impulse in N s, or a force in N for one physics step
impulseNoTrue for an impulse in N s, False for a force in N for one physics step. For a sustained push, give an impulse of force times seconds
positionNoWorld-space point to push at; the body's centre of mass when omitted
prim_pathYesThe rigid body's prim path, a robot's link among them

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • changedInput schema / properties / prim_path / description
      Previous value: -"The rigid body's prim path"New value: +"The rigid body's prim path, a robot's link among them"
  2. First observedv0.2.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare non-read-only, non-destructive, closed-world; the description goes far beyond that by disclosing articulation/link behaviour, friction effects, the tensor-API path under suppressReadback, the replace-on-second-push semantics before the next physics step, and the exact refusal conditions.

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?

Front-loaded with the core action and the key distinction from the sibling, then progresses through behaviour, caveats, and refusals. It is dense and long, but nearly every sentence carries operational information; minor tightening is possible.

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

Completeness5/5

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

An output schema exists, yet the description still sketches the answer (point pushed at, path taken, method: physx vs tensor). Combined with the edge-case coverage, nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so force/impulse/position/prim_path are already documented, including the impulse-vs-force meaning and the centre-of-mass default. The description reinforces the physical interpretation ('its mass counts', impulse over whole mass) but adds no syntax or format details beyond the schema, making the baseline 3 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?

States a specific verb and resource – pushing a rigid body through PhysX with force or impulse – and immediately distinguishes it from set_prim_transform ('To place a body rather than push it'). An agent can tell which sibling to use without inspecting schemas.

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

Usage Guidelines5/5

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

Explicit preconditions (simulation playing or paused), explicit exclusions (no RigidBodyAPI, disabled/kinematic bodies, bodies fixed to the world), an explicit alternative for positioning, and guidance to combine pushes into one per step. This is close to exhaustive routing information.

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