FINLY Balance Report Analysis

Delete report analysis | מחיקת תוצאת ניתוח

delete_report_analysis_result

DestructiveIdempotent

Cancel this operation and delete its encrypted result using its exact capability. A deleted operation cannot be restarted. No raw report, identity or result is placed in the URL.

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": {
      "operation": "<operation>"
    },
    "name": "delete_report_analysis_result"
  }
}

Input Schema

Name	Required	Description	Default
`operation`	Yes

Output Schema

Name	Required	Description	Default
`tool`	Yes
`as_of`	Yes
`result`	No
`status`	Yes
`receipt`	Yes
`evidence`	No
`no_action`	No
`request_id`	Yes
`assumptions`	Yes
`limitations`	Yes
`next_actions`	Yes
`response_kind`	Yes
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 10, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already cover destructive and idempotent hints, so the description adds value by noting irreversibility ('cannot be restarted') and the URL privacy guarantee. However, it does not disclose whether the operation record itself is deleted or only the result, leaving minor ambiguity.

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?

Two sentences with no fluff, purpose is front-loaded. Every word contributes to meaning, and the description is efficient.

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?

With zero schema descriptions and no parameter explanations, the description is insufficient for an agent to correctly invoke the tool without external knowledge. It lacks guidance on obtaining the handle/token and the output format, though the output schema exists to cover return values.

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 description coverage is 0%, so the description must compensate, but it only mentions 'exact capability' without explaining result_handle or result_token. An agent cannot infer parameter purposes from the description alone, especially since both are required in a nested object.

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 states it cancels the operation and deletes its encrypted result, which is a clear destructive action. It differentiates from siblings (analyze, get) through the verb 'delete', though it does not explicitly name alternatives. The title reinforces the purpose.

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 explicit guidance on when to use this tool versus get_report_analysis_result or analyze_balance_report. The description only warns that deletion cannot be restarted, but does not state use cases, prerequisites, or exclusions. Usage is implied but not clarified.

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

All FINLY Balance Report Analysis tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?