Skip to main content
Glama
PaulMRamirez

Yamcs MCP Server

by PaulMRamirez

commands_run_command

Execute a command on Yamcs by providing the command name and optional arguments. Supports dry run for validation before execution.

Instructions

Execute a command on Yamcs.

To execute SWITCH_VOLTAGE_OFF with voltage_num=1, call this tool with: command="/YSS/SIMULATOR/SWITCH_VOLTAGE_OFF" args={"voltage_num": 1}

To execute with multiple arguments: command="/YSS/SIMULATOR/SOME_CMD" args={"arg1": "value1", "arg2": 123}

The args parameter should be a dictionary mapping argument names to values. If you pass a JSON string, it will be automatically parsed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoDictionary of command arguments like {"voltage_num": 1} or JSON string '{"voltage_num": 1}'
commandYesFull qualified command name like /YSS/SIMULATOR/SWITCH_VOLTAGE_OFF
commentNoOptional comment for the command
dry_runNoIf true, validate without executing
instanceNoYamcs instance name
processorNoProcessor name, usually "realtime"realtime
sequence_numberNoOptional sequence number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description bears full burden. It indicates the tool modifies state (execute command) and supports dry_run for validation. Lacks details on side effects, authorization, or error handling.

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?

Relatively short and front-loaded with main action. Examples are helpful but add length; still efficient for the information provided.

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 7 parameters and full schema coverage, description covers essential aspects. With output schema present, return values need not be explained. Minor gap: no mention of execution output or follow-up.

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 coverage is 100%, baseline 3. Description adds value by showing exact args format (dictionary or JSON string) and automatic parsing, exceeding schema descriptions.

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 'Execute a command on Yamcs' with specific verb and resource. Examples distinguish it from sibling tools like commands_describe_command.

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?

Provides detailed examples on how to use the tool, including syntax for command and args. However, it does not explicitly compare with alternatives or state when not to use it.

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/PaulMRamirez/yamcs-mcp-server'

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