Skip to main content
Glama
Sign In
PhySpace-Forge

PhySpace-Forge

by jason12343
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

physpace_step_realtime_safety_shield

Runs one 5 ms closed-loop robot safety-shield step by filtering raw VLA gripper closing commands against the object's Golden Safety Corridor, returning a safe actuator command and tactile array.

Instructions

Execute one 5ms (200Hz) real-time closed-loop step on the robot safety shield. Filters a raw VLA gripper closing action (mm) against the object's Golden Safety Corridor and returns the safe actuator command + hardware-aligned tactile array.

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": {
      "object_id": "<object_id>",
      "raw_vla_closing_delta_mm": "<raw_vla_closing_delta_mm>",
      "measured_peak_pressure_kpa": "<measured_peak_pressure_kpa>"
    },
    "name": "physpace_step_realtime_safety_shield"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_idYesObject currently being manipulated.
is_liftingNoWhether the robot arm is currently lifting the object.
raw_vla_closing_delta_mmYesRaw gripper closing delta command from VLA policy (mm).
measured_peak_pressure_kpaYesCurrent measured fingertip peak pressure in kPa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral-disclosure burden. It usefully states the 5ms/200Hz timing and that the tool returns a safe actuator command plus tactile array, but it does not clarify whether it actuates hardware or only computes a filtered command, what state it mutates, or what happens when the Golden Safety Corridor is violated.

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

Conciseness5/5

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

The description is two tightly written sentences with no filler. It front-loads the core action and then specifies the filtering behavior and return values, making it easy to scan.

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 safety-critical real-time step tool with no annotations and no output schema, the description provides the essential action, timing, filtering logic, and return contents. It still omits prerequisites, statefulness or side effects, failure behavior, and sibling differentiation, which are important for correct invocation.

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 100%, so all four parameters are already documented in the input schema. The description adds contextual meaning by tying the raw closing delta to the object's Golden Safety Corridor, but it does not add parameter-specific syntax, constraints, or defaults beyond what the schema provides.

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 uses a specific verb and resource: executing a 5ms real-time closed-loop step on the robot safety shield, filtering a raw VLA gripper closing action against the Golden Safety Corridor. It is clear what the tool does, but it does not explicitly distinguish this step tool from sibling tools such as physpace_inspect_object_safety_envelope or physpace_simulate_grasp_trajectory.

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 description implies usage in a real-time closed-loop control flow by stating it executes one 5ms step and filters a raw VLA action. However, it gives no explicit when-to-use guidance, no when-not-to-use conditions, and no alternatives among the sibling safety-envelope or trajectory tools.

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