Skip to main content
Glama
wkqco33

remote-ros-mcp

by wkqco33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ros2_action_send_goal

Send a goal to a ROS2 action server and wait for the result, enabling remote control and verification of robotics applications.

Instructions

Send a goal to a ROS2 Action server and optionally wait for result.

    Args:
        action_name: Name of the action (e.g. '/navigate_to_pose')
        action_type: Action type identifier (e.g. 'nav2_msgs/action/NavigateToPose')
        goal_data: Goal definition as JSON dict
        wait_for_result: Whether to block until goal completes or times out
        timeout_sec: Maximum timeout to wait for result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goal_dataYes
action_nameYes
action_typeYes
timeout_secNo
wait_for_resultNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It explicitly discloses blocking behavior via wait_for_result, timeout semantics via timeout_sec, and the optional wait-for-result design. It does not describe error behavior or what happens to a running goal when not waiting, but the core blocking and timing traits are transparent.

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 front-loaded with a one-sentence purpose followed by a compact Args list. Every line adds useful meaning, with no filler or redundant restatement of the tool name.

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?

Given the existence of an output schema, return-value details are not required here. The description covers all parameter semantics and the send/wait behavior needed to make a basic call. The main gap is not addressing what the agent should do when wait_for_result is false or when the action should be canceled instead.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates by explaining every parameter. It gives concrete examples for action_name and action_type, clarifies goal_data as a JSON dict, and defines the semantics of wait_for_result and timeout_sec well beyond their generic schema titles.

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?

The description opens with 'Send a goal to a ROS2 Action server and optionally wait for result,' which uses a specific verb and resource. This clearly distinguishes the tool from sibling actions like ros2_action_cancel_goal or topic publishing tools.

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 intended use is implied through the action-send terminology and the parameter explanations, but the description does not explicitly state when to prefer this over ros2_action_cancel_goal or other ROS2 interaction tools. There is no when-to-use / when-not-to-use guidance.

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