Skip to main content
Glama

Particle Report Delete

particle_report_delete
Destructive

Delete a saved Radar report for everyone in the project. Any member of the project's organization may delete one. Its Radar link stops opening it, so do this only when the user asks.

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": {
      "report_id": "<report_id>"
    },
    "name": "particle_report_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYesReport id to delete.
output_formatNoOutput serialization. 'markdown' (default) returns the LLM-facing rendering. 'json' returns the structured payload as JSON text — use only for programmatic chaining where exact field extraction matters; the JSON shape is larger and noisier for an LLM to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, but the description adds blast radius ('for everyone in the project'), an authorization rule, and an observable consequence ('Its Radar link stops opening it') that the agent could not infer from the structured fields. It does not say whether deletion is recoverable or what it returns.

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?

Three short sentences, front-loaded with the action and scope, followed by permission and a caution. No redundant restatement of the title or annotations.

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 two-parameter destructive tool with no output schema, the definition covers scope, permissions, consequence, and hesitation guidance. It leaves only reversibility and error behavior unstated, which are minor for a straightforward delete.

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 both report_id and output_format are already documented in the schema, and the description adds no further meaning to either. Baseline 3 is appropriate here.

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 ('Delete a saved Radar report') and adds scope ('for everyone in the project'), which separates it from particle_report_get/list/update without naming them. It stops short of explicitly pointing to a sibling for the non-destructive path.

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 an explicit when-not ('do this only when the user asks') and states who is permitted ('Any member of the project's organization may delete one'). What's missing is the alternative action to recommend instead, e.g. particle_report_update when the user only wants to change a report.

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