Skip to main content
Glama
erikrubstein

monarch-mcp2

by erikrubstein

Reports Delete Saved Report

reports_delete_saved_report
Destructive

Delete a saved report by specifying its report ID. Optionally clear the session path and choose output format (summary, full, raw).

Instructions

Delete saved report. This may delete, clear, reset, or otherwise remove data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
report_idYes
output_modeNoOutput shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.summary
session_pathNo
Behavior2/5

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

Annotations already mark destructiveHint: true. The description adds 'This may delete, clear, reset, or otherwise remove data,' which is redundant and adds no new behavioral insight. No information about irreversibility, permissions, or side effects.

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?

Very concise at two sentences, but the second sentence is redundant with the annotation. Could be improved by removing the second sentence or merging it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

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

For a deletion tool with 4 parameters and no output schema, the description lacks important context: required parameter (report_id), behavior on success/failure, any confirmation or undo options, and output shape. Incomplete for a user to fully understand the operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 50% description coverage (fields and output_mode have descriptions; report_id and session_path do not). The tool description does not add any parameter information, failing to compensate for the missing schema descriptions.

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?

Description clearly states the tool deletes a saved report. The verb 'delete' is specific and distinguishes it from sibling tools like reports_get_saved_report or reports_list_saved_reports.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, such as when to use reports_delete_saved_report vs reports_update_saved_report or other deletion tools. No prerequisites or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/erikrubstein/monarch-mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server