Skip to main content
Glama
Sign In
PhySpace-Forge

PhySpace-Forge

by jason12343
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

physpace_inspect_object_safety_envelope

Query calibrated SI material parameters and the Golden Grasp Safety Corridor for a 3D object before robotic grasping to prevent slip and crushing.

Instructions

Query the calibrated SI continuum constitutive parameters (Young's modulus E, Poisson's ratio nu, yield stress sigma_y, static/dynamic friction mu_s/mu_d) and the Golden Grasp Safety Corridor [P_slip_min_kpa, P_crush_max_kpa] for a 3D object before executing a robotic grasp.

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>"
    },
    "name": "physpace_inspect_object_safety_envelope"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_idYesTarget object identifier (e.g., 'tapered_coffee_cup', 'soft_silken_tofu', 'ripe_strawberry', 'avian_fresh_egg', 'corrugated_parcel_box', 'silicone_bellows_valve').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does good work by naming units (SI, kPa) and the exact quantities returned, implying a read-only, non-mutating lookup. It says nothing about behavior for an unknown or uncalibrated object_id, whether values are cached/versioned, or how the corridor is derived, leaving meaningful gaps for a safety-critical call.

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?

One dense sentence with the action front-loaded and the payload enumerated without filler. The parenthetical symbol lists and bracketed corridor notation are information-bearing rather than padding, though the phrase 'calibrated SI continuum constitutive parameters' front-loads jargon before the plain meaning arrives.

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

Completeness4/5

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

There is no output schema, so the description must convey return values, and it does: it names every constitutive quantity and both corridor bounds. For a single-parameter lookup that is nearly complete; the missing piece is failure/empty-result semantics when an object is not in the calibrated library.

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% and the schema's object_id description already supplies illustrative examples, so the schema does the heavy lifting. The description adds no extra meaning about the parameter — no naming conventions, no behavior when the ID is absent from the calibrated library. Baseline 3 applies.

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 ('Query') and enumerates the exact resource returned: Young's modulus, Poisson's ratio, yield stress, static/dynamic friction, plus the Golden Grasp Safety Corridor bounds. That level of specificity makes the tool clearly a pre-grasp property lookup rather than a simulation or control tool, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

It gives a clear workflow position: call this 'before executing a robotic grasp.' That is real when-to-use context for an agent. It stops short of exclusions or routing to alternatives such as physpace_simulate_grasp_trajectory or physpace_step_realtime_safety_shield, so it falls short of a 5.

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