remote-ros-mcp

Overview Schema Source Related Servers Discussions Admin

ros2_topic_echo

Capture and return messages from a ROS2 topic by specifying its name, type, count, and timeout. Enables remote inspection of ROS2 communications without a local ROS2 installation.

Instructions

Capture and return messages from a ROS2 topic.

    Args:
        topic: Topic name to listen to (e.g. '/robot/cmd_vel')
        topic_type: Message type (e.g. 'geometry_msgs/msg/Twist')
        count: Number of messages to capture (default 1)
        timeout_sec: Maximum time to wait in seconds

Input Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`topic`	Yes
`topic_type`	Yes
`timeout_sec`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 19, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose blocking semantics, timeout behavior (e.g., what happens if fewer than 'count' messages arrive), handling of non-existent topics, or whether it subscribes transiently. The only behavioral hint is the timeout_sec parameter.

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 purpose is front-loaded in a single sentence, followed by a structured Args list with no wasted words. The docstring format is efficient and scannable for an agent.

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?

An output schema exists, so return-value explanation is not required. However, with 0% schema coverage and no annotations, the description should cover edge behavior more thoroughly — specifically timeout behavior, empty-topic handling, and what 'capture' implies about subscription semantics. It covers the basics but leaves operational details to inference.

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% — the schema contains only titles, no descriptions. The description's Args list is the sole source of parameter meaning and covers all 4 parameters with brief but functional definitions, including defaults for count and timeout_sec. Could add format details (e.g., message type syntax) but adequately compensates for the empty schema.

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 states a specific verb ('Capture and return') and resource ('messages from a ROS2 topic'), which clearly identifies the tool's function. It implicitly distinguishes from the publish sibling (receive vs send) and get_topics (sample vs list), though it does not explicitly name any sibling.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. With 15 siblings including ros2_measure_topic_hz (which also subscribes and samples a topic) and ros2_assert_topic_published, an agent gets no help selecting among overlapping capabilities.

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

Deploy Server