Skip to main content
Glama

Particle Report List

particle_report_list
Read-only

List the saved Radar reports in your project, most recently edited first, each with its id, subjects and Radar link. Feed an id into particle_report_get for its full settings, particle_report_update to change it, or particle_report_delete. Check here before creating a report the project may already have.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "particle_report_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoReports per page (1-100, default 25).
cursorNoOpaque pagination cursor from a previous response's cursor field.
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/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds real context beyond them: deterministic ordering (most recently edited first) and the exact fields each row carries. It doesn't discuss paging behavior in prose, but the schema documents limit and cursor fully.

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 sentences, each doing distinct work: what it returns and in what order, where to go next with an id, and the duplicate-check call to action. 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.

Completeness5/5

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

With no output schema, the description compensates by naming the returned fields, and all three parameters are documented in the schema. For a zero-required-parameter read-only list tool, an agent has everything needed to call it correctly and to chain into the get/update/delete siblings.

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%, and the schema itself explains limit bounds, cursor provenance, and the markdown-vs-json tradeoff in detail. The description adds no parameter guidance of its own, so the baseline 3 applies.

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?

States a specific verb and resource ("List the saved Radar reports in your project") plus the sort order (most recently edited first) and the fields returned (id, subjects, Radar link). This clearly separates it from particle_report_get, which returns full settings for a single report.

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?

Explicitly routes the agent: an id from this list feeds particle_report_get for settings, particle_report_update to change, or particle_report_delete. It also gives a pre-emptive check ("Check here before creating a report the project may already have"), naming particle_report_create as the alternative to avoid duplicating.

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