Skip to main content
Glama

Particle Report Get

particle_report_get
Read-only

Get one saved Radar report: its name, subjects, period, sources and presentation settings, and its Radar link. The report's mentions and news are read on its Radar page, not returned here; to answer from the data, use the podcast tools on the same subjects.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYesReport id from particle_report_list or particle_report_create.
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
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful boundary — that mention/news content is excluded from the payload — but says nothing about failure behavior when a report_id is invalid or about what happens with expired/deleted reports.

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?

Two tightly built sentences: the returned content is front-loaded, then the scope limitation and alternative path. No filler, though the second sentence carries two distinct ideas (exclusion + redirect) that could be split for faster scanning.

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 two-parameter read tool with no output schema, the description supplies the return-content inventory, the deliberate exclusion, and the fallback route. Nothing an agent needs in order to call it correctly or interpret the result is missing.

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 coverage is 100% and the schema itself already explains that report_id comes from particle_report_list or particle_report_create and that output_format trades LLM readability against structured extraction. The description adds no parameter meaning beyond that, so 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?

The description names a specific verb and resource ('Get one saved Radar report') and enumerates the returned contents — name, subjects, period, sources, presentation settings, Radar link — which distinguishes it cleanly from the create/list/update/delete siblings.

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 explicitly states what this tool will NOT answer ('mentions and news are read on its Radar page, not returned here') and redirects the agent to the podcast tools for data-driven answers. The exclusion is precise, though the alternative is named as a family rather than a specific sibling tool.

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