Skip to main content
Glama
Yutarop
by Yutarop

call_ros2_service

Invoke a ROS 2 service to control robot behavior. Specify service name, type, and optional request payload for actions like setting pen or clearing environment.

Instructions

Calls a ROS 2 service with the specified name, type, and optional request.

Args:
    service_name: Name of the service to call.
    srv_type: Type of the service (e.g., "std_srvs/srv/Empty").
    request: Request payload in string format (e.g., "{r: 255, g: 0, b: 0, width: 2, off: 0}").
             If the service type does not require a request (e.g., std_srvs/srv/Empty),
             this can be omitted or set to None.

Example:
    Call a service without a request:
        service_name = "/clear"
        srv_type = "std_srvs/srv/Empty"

    Call a service with a request:
        service_name = "/turtle1/set_pen"
        srv_type = "turtlesim/srv/SetPen"
        request = "{r: 255, g: 0, b: 0, width: 2, off: 0}"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestNo
srv_typeYes
service_nameYes
Behavior3/5

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

No annotations are provided, so the description carries the burden. It explains the parameters and gives examples but does not disclose potential side effects, synchronous behavior, or authorization requirements. The description is adequate but could be more transparent.

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 description is front-loaded with the purpose and uses a clear docstring format with Args and Example sections. It is slightly verbose but structured effectively.

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 no annotations or output schema, the description covers the main aspects: what the tool does, parameter explanations, and usage examples. It lacks return value or error handling information, but overall it is fairly complete.

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

Parameters5/5

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

Schema description coverage is 0%, but the description thoroughly explains each parameter, provides the format for request (string), and explains when request can be omitted (Empty service type). This adds significant meaning beyond the schema's titles alone.

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 clearly states the verb 'calls' and the resource 'ROS 2 service', and it is easily distinguishable from sibling tools like 'list_ros2_services' or 'publish_ros2_topic'.

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?

The description provides clear context for when to use the tool, including examples with and without a request payload. However, it does not explicitly mention when not to use it or compare with sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Yutarop/ros-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server