Rollstack

Update burst filters

updateBurstFilters

DestructiveIdempotent

Replaces the filters an older report's burst varies by, then writes every variant's values into its syncs again, which can take a minute, and answers the burst. A filter left out is removed with every variant's value of it, unless replace carries those values to its new filter: confirm with the user first. Variants keep their files and names. Only the burst's owner and admins may. A Rollstack report's burst varies by report parameters and returns 400.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>",
      "body": "<body>"
    },
    "name": "updateBurstFilters"
  }
}

Input Schema

Name	Required	Description
`body`	Yes
`params`	Yes
`idempotencyKey`	No	A unique value, such as a UUID, that makes retrying this call safe. A retry with the same key within 24 hours answers the first call's result instead of running it again. Use a new key for each new call. From 1 to 255 printable ASCII characters.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations mark this destructive, but the description adds behavior the hint cannot express: the call can take a minute, variants keep their files and names, omitted filters lose every variant's value irreversibly, only the owner or admin may call it, and Rollstack reports are rejected with 400. What is missing is what the response contains ('answers the burst' is vague), so a 5 is not warranted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical destructive warning is front-loaded, which is good, but the opening sentence is a run-on ('...writes every variant's values into its syncs again, which can take a minute, and answers the burst'), and 'Only the burst's owner and admins may.' is a truncated clause that forces the reader to supply the verb.

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?

For a destructive, slow, permission-gated mutation with no output schema, the description covers timing, irreversibility, authorization, and one known error path. The remaining gap is the return value, which the description leaves as the opaque phrase 'answers the burst'.

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?

The input schema already documents body.replace, primaryIds, secondaryIds and params.id in detail, and the description mostly restates the schema's own warning about omitted filters. Schema description coverage is reported at 33%, but the description adds little beyond what those nested property descriptions already say.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Replaces the filters an older report's burst varies by', and adds that sync values are rewritten. It is clearly distinct from addBurstVariants or renameBurst, but it never names the closest sibling, reapplyBurstFilters, so the agent must infer the difference.

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

Usage Guidelines3/5

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

There is conditional guidance embedded in the text: a filter omitted is deleted irreversibly 'unless replace carries those values to its new filter: confirm with the user first', and Rollstack reports return 400. There is no explicit routing guidance such as when to use this versus reapplyBurstFilters, which reads similarly but is presumably less destructive.

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

All Rollstack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?