Skip to main content
Glama

Filters Rename

filters_rename
Destructive

Renames saved filters by exact ID in one report-resource write, using a report content fingerprint to prevent conflicts and preserve definitions, bindings, and other resources.

Instructions

Rename saved filters by exact ID in one report-resource write.

Get report_content_fingerprint from filters_list. Preserves definitions, IDs, bindings, other resources and report-level components/concepts. A rename may affect labels on many consumers; preview lists saved references. No name matching, source editing or automatic publication. Durable journal, conflict preflight, independent read-back and operation_restore. Does not change filter conditions or create/delete a filter. Unknown outcomes are not retried.

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": {
      "changes": "<changes>",
      "expected_report_content_fingerprint": "<expected_report_content_fingerprint>"
    },
    "name": "filters_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
dry_runNo
report_idNo
expected_report_content_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.3/5.0
Behavior5/5

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

Well beyond the annotations, it discloses preservation guarantees (definitions, IDs, bindings, other resources, report-level components/concepts), blast radius (labels on many consumers, preview of saved references), and the safety machinery (durable journal, conflict preflight, independent read-back, operation_restore, no retry on unknown outcomes). This is exactly the mutation-side context annotations cannot convey.

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?

Front-loaded with the action and the fingerprint prerequisite, then a compressed block of guarantees and exclusions. Every clause carries information, though the telegraphic fragment style ("Durable journal, conflict preflight, independent read-back and operation_restore.") reads as a list dump rather than prose.

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?

An output schema exists, so return values needn't be described, and the mutation's risk profile is thoroughly covered. The notable omission is that dry_run defaults to true, meaning a call without it previews rather than commits — a behavior an agent needs to know to invoke this correctly.

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?

With 0% schema description coverage the description must carry the load, and it does explain the fingerprint's provenance and the exact-ID semantics of filter_id. However, dry_run (default true), report_id, and the per-change object shape are never characterized, so roughly half the surface remains undocumented in both schema and prose.

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 opening sentence names a specific verb and resource ("Rename saved filters") plus the addressing mechanism ("by exact ID") and scope ("in one report-resource write"). It is immediately distinguishable from filters_update_conditions, filters_create, and filters_delete, which the description explicitly rules out.

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?

It gives a concrete prerequisite (fetch report_content_fingerprint via filters_list) and clear negative scope: no name matching, no source editing, no automatic publication, no condition changes, no create/delete. It stops short of naming which sibling to use for the excluded operations, leaving routing partly implicit.

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