Skip to main content
Glama
YidaYang

embodify-mcp

by YidaYang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reset_task

Starts a new robot simulation episode, optionally selecting suite, task, and initial layout, and returns run ID, task details, images, robot state, and step info.

Instructions

Start a new FakeSim episode. All three arguments are optional: omit them all to use the server's default scene (usually task 0 of the suite with initial layout 0), which is the most common use. To switch tasks, use list_tasks first: without arguments it lists the suites, with suite it gives the task_index and instruction of every task in that suite; then pass the chosen suite / task_index. init_state_index picks another object layout of the same task. If the server was started with --lock-task (task_locked is true in get_session_info), passing any of these arguments returns a task_locked error. If an episode is already running, returns already_running; call stop_episode first. Returns run (short run ID), task (suite, task_index, name, instruction, init_state_index), images (agentview and robot0_eye_in_hand: two separate PNGs), state (eef_pos_m is the end-effector XYZ position in meters; eef_rpy_rad.roll_x, pitch_y and yaw_z are the orientation about the robot base X/Y/Z axes in radians; gripper.command is the open/close target and gripper.opening_m the gripper opening in meters), step (simulation steps used) and steps_left (simulation steps left in this episode).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suiteNoSwitch to another suite; omit to keep the current one. See list_tasks (without arguments) for the suites.
task_indexNoWhich task of the suite; omit to use the server's default scene (task 0 when switching suites). See list_tasks with suite for the options.
init_state_indexNoWhich initial layout of the task; 0 if omitted. Must be below the task's n_init_states.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses two distinct failure modes (task_locked, already_running), the precondition that stop_episode must precede it, default-argument behavior, and the full shape of the return payload. This is far beyond what a bare 'reset' would convey.

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?

The most important fact — that all three arguments are optional and omitting them is the common path — is bolded and front-loaded, which is well judged. The trailing enumeration of the return payload is long and reads as a run-on, but it is justified because no output schema exists.

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?

With no annotations and no output schema, the description must supply safety, preconditions, error behavior, and return semantics on its own — and it does all four, including unit-bearing field explanations (eef_pos_m, eef_rpy_rad, gripper.opening_m). 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 description coverage is 100%, so the schema already documents suite, task_index, and init_state_index including their defaults and the n_init_states bound. The description largely restates that ('init_state_index picks another object layout', task 0 default) rather than adding new syntax or constraints, so the baseline 3 applies.

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?

Opens with a specific verb and resource ('Start a new FakeSim episode') and immediately clarifies the scope of the operation (fresh episode, not a continuation). An agent can distinguish it from stop_episode, observe, and get_session_info without opening any schema.

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 routing: omit all args for the default scene, call list_tasks first to switch tasks (and it even explains what list_tasks returns with and without args), and call stop_episode first if an episode is already running. The --lock-task precondition is stated as a when-not condition.

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