Skip to main content
Glama
rrvrs

jira-alerts-mcp

by rrvrs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Attach key/value properties to a JSM alert

jsm_add_alert_extra_properties
DestructiveIdempotent

Attach or overwrite key/value properties on a JSM alert to store structured context like runbook links or region tags for programmatic use.

Instructions

Attach arbitrary key/value context to a JSM alert, or overwrite properties already on it.

Extra properties are the structured half of an alert, next to the prose in its description: a runbook link, the region, the deploy that preceded it, a trace id. Unlike a note they can be read back programmatically by whatever picks the alert up next.

Args:

  • alert_id (string): the full alert id (not the tinyId)

  • extra_properties (object): key/value pairs; values may be strings, numbers or booleans

Returns: { "requestId": string, "result": string, "alert_id": string }

IMPORTANT: this action is asynchronous. Verify with jsm_get_request_status using the returned requestId.

This merges by key: keys not mentioned are left alone, and a key that already exists is overwritten without warning. Read the alert first with jsm_get_alert if you need to know what a key currently holds.

Examples:

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
alert_idYesFull alert id, e.g. '9b251e07-73c9-4907-9996-8cb53a6a20d0-1704440650350'. This is NOT the short tinyId shown in the JSM UI — get the full id from jsm_list_alerts first.
extra_propertiesYesKey/value context to attach, e.g. {'runbook': 'https://…', 'region': 'us-east-1'}. A key that already exists is overwritten.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo
alert_idYes
requestIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv2.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the call is asynchronous, that it merges by key, and that an existing key is overwritten without warning. These are non-obvious operational traits an agent must know, and they are stated directly rather than left to inference.

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?

It is front-loaded with the purpose, then structured into args, returns, an async warning, merge semantics, and an example. Every block is informative, though the args/returns restatements overlap with the schema and the trailing example is truncated, adding minor redundancy.

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

Completeness5/5

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

For an async mutation tool with a nested object param and an output schema, the description covers the async requirement, the verification path, the overwrite/merge semantics, and pre-read guidance. Nothing an agent needs to call it correctly is missing.

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%, so both params are already documented, but the description reinforces the critical alert_id vs tinyId distinction and adds a worked example mapping a natural-language request to the extra_properties object. The added example value slightly exceeds the schema-only baseline.

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 states a specific verb and resource ('Attach arbitrary key/value context to a JSM alert') and distinguishes the action from sibling tools by contrasting it with notes ('the structured half of an alert, next to the prose in its description'). An agent can select it over jsm_add_alert_note or jsm_update_alert_field without further reading.

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

Usage Guidelines5/5

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

It names concrete use cases (runbook link, region, deploy, trace id), gives the alternative behavior (prose notes vs programmatic properties), and routes to two follow-up tools: read first with jsm_get_alert and verify with jsm_get_request_status. This is explicit when-to-use and what-to-do-next 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