Skip to main content
Glama
PaulMRamirez

Yamcs MCP Server

by PaulMRamirez

alarms_unshelve_alarm

Reactivate a previously shelved alarm to resume monitoring and alerting.

Instructions

Unshelve (reactivate) a previously shelved alarm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
alarmYesAlarm name
commentNoOptional unshelve comment
instanceNoYamcs instance (uses default if not specified)
processorNoProcessor name (default: realtime)realtime
sequence_numberYesAlarm sequence number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It omits important behavioral details: side effects (state change), permissions required, whether operation is reversible, or any return values despite an output schema existing.

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?

Extremely concise single sentence that front-loads the core action without any wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite an output schema existing, the description does not mention return values. It also lacks prerequisites (alarm must be shelved) and any behavioral context for a state-modifying operation, making it incomplete for a tool with 5 parameters.

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 each parameter is already documented. The description adds no additional meaning beyond the schema, earning the baseline score of 3.

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 action 'Unshelve (reactivate)' and the resource 'previously shelved alarm', distinctly differentiating it from sibling tools like alarms_shelve_alarm. The verb+resource combination is specific and unambiguous.

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 on when to use this tool versus alternatives. It does not mention that the alarm must be in a shelved state first, nor does it provide any context about prerequisites or conditions for use.

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