Skip to main content
Glama

manage_suppression_rule

Add, retarget, remove or dry-run one suppression rule of the caller's account, chosen by action. A matched issue keeps recording events and keeps its status while staying out of the default list and out of every notification. To silence a set of issues: call this with action=preview and the match and conditions, read the sample back to the person (call again with page=1 and the same match and conditions when issuesMatched is larger than one page), then call this with action=create and that same match and those same conditions, then call list_suppression_rules to see how much the new rule covers. A rule the account already holds is refused, so read the existing rules before adding one. To retarget a rule that is too wide, too narrow or simply wrong: call list_suppression_rules to read the rule ids, their conditions and their coverage, call this with action=preview and the match and conditions you mean to move it to, then call this with action=update, the id and that same match and those same conditions; a rule is replaced whole, so send every condition it should keep, and it keeps its id, its author and the day it was added. To remove a rule: call list_suppression_rules for the id, then call this with action=delete and that id. On update and delete, issues the old conditions hid return to the list at once and alert again on their next event; nothing is resent for issues that stay quiet, cards withheld while the rule was in force are not resent, and the answer reports how many issues are now waiting to alert again as rearmedIssues. A preview stores nothing and changes no issue: its answer holds how many issues the conditions match, how many of those were seen in the last day, and one page of matching issues, most recently seen first. To silence a single issue instead (the app calls this suppressing one issue), call set_issue_status with IGNORED. A rule holds one to five conditions and one operator: match="all" covers an issue only when every condition holds, match="any" covers it as soon as one does. A rule of one condition has nothing to join, so it is stored and answered as match="all" whichever operator you sent. A condition is a field and a value. Every field matches the whole value, case insensitive, and a star stands for any run of characters: service notifier names that one service, exceptionType java.net.* names every type under java.net, title timed out names every title carrying that phrase, level warn names every issue recorded at that severity. An ENVIRONMENT condition matches an issue that has been seen in a deployment environment matching the value, so a rule naming one environment covers the whole issue, not only that environment's rows. A value of only stars is refused. To narrow, write match="all" with conditions [{"field":"SERVICE","value":"notifier"},{"field":"ENVIRONMENT","value":"staging"},{"field":"LEVEL","value":"warn"}], which covers the notifier service's warnings in staging and nothing else. To widen, write match="any" with conditions [{"field":"EXCEPTION_TYPE","value":"com.slack."},{"field":"EXCEPTION_TYPE","value":"io.netty."}], which covers both libraries. A condition can be negated: to cover everything from payments except timeouts, write match="all" with conditions [{"field":"SERVICE","value":"payments"},{"field":"EXCEPTION_TYPE","value":"java.util.concurrent.TimeoutException","negated":true}], and an issue carrying no exception type at all counts as not a timeout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe rule id (from list_suppression_rules); needed by update and delete, ignored by create and preview
pageNopreview only: page of matching issues to read, 0 to 1000 (default 0); a page beyond that is refused
sizeNopreview only: issues per page, 1 to 50 (default 10)
matchNoall or any; needed by create, update and preview
actionYescreate, update, delete or preview
conditionsNoOne to five conditions, each a field (SERVICE, ENVIRONMENT, EXCEPTION_TYPE, TITLE or LEVEL), a value of 1 to 200 characters in which a star stands for any run of characters, and an optional negated flag, false unless you send it, which turns the condition into is not; needed by create, update and preview

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Changed1 schema field changed
    • changedInput schema / properties / conditions / description
      Previous value: -"One to five conditions, each a field (SERVICE, ENVIRONMENT, EXCEPTION_TYPE or TITLE), a value of 1 to 200 characters in which a star stands for any run of characters, and an optional negated flag, false unless you send it, which turns the condition into is not; needed by create, update and preview"New value: +"One to five conditions, each a field (SERVICE, ENVIRONMENT, EXCEPTION_TYPE, TITLE or LEVEL), a value of 1 to 200 characters in which a star stands for any run of characters, and an optional negated flag, false unless you send it, which turns the condition into is not; needed by create, update and preview"
  8. Added
  9. Removed
  10. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it goes far beyond basic mutation: it explains that suppressed issues still record events, update/delete rearm issues and report rearmedIssues, preview is side-effect free, one-condition rules are normalized to match='all', ENVIRONMENT matches at issue level, and star-only values are refused. These details reveal edge-case behavior an agent would otherwise discover only through failures.

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 long but methodically organized by action workflow and matching semantics, with concrete examples. Every section contributes essential execution knowledge, so the length is justified; it earns a 4 rather than 5 because it is verbose enough that a purely token-conscious agent might need to parse carefully, but the structure is clear and front-loaded.

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 a tool with no output schema and six parameters, the description covers all necessary operational context: precondition steps, parameter requirements per action, exact return metrics (issuesMatched, rearmedIssues), and edge cases like negation and empty values. An agent has enough information to execute every action correctly without external lookups.

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?

Although schema coverage is 100%, the description adds substantial semantic meaning: it explains match operators, condition fields and values, wildcards, negation semantics, and the interaction of ENVIRONMENT conditions with issue-level matching. It also clarifies which parameters each action requires, such as id for update/delete and page for previews, enriching the schema far beyond its field 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 opens with a specific multi-verb purpose 'Add, retarget, remove or dry-run one suppression rule of the caller's account, chosen by action,' naming both the resource and all supported actions. It clearly distinguishes itself from sibling read tools like list_suppression_rules and from single-issue silencing via set_issue_status, so an agent can select it without ambiguity.

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?

The description gives explicit step-by-step workflows for create, update, delete, and preview, including when to call list_suppression_rules first to read existing rules or ids dove. It also tells agents when not to use this tool ('To silence a single issue... call set_issue_status with IGNORED') and names the alternative, satisfying the when/when-not requirement completely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources