FINLY Balance Report Analysis

Report analysis requirements | דרישות לניתוח דוח יתרות

get_report_analysis_requirements

Get the processing notice, external OCR supplier notices for existing-task authority or legacy approval, and a single-use proof-of-work challenge. Normal report analysis requires no additional FINLY approval. Solve SHA-256(challenge_token + ":" + proof) so its first two bytes are zero.

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": "get_report_analysis_requirements"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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

A4.1/5.0

Behavior4/5

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

Annotations are all false, so the description carries the burden. It discloses the proof-of-work requirement in detail (SHA-256 with zero first two bytes), critical behavior for correct invocation. It doesn't mention return format or per-use nature beyond single-use challenge, but the proof-of-work detail is significant and transparent.

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, front-loaded with the purpose, and each sentence adds value: core deliverables, approval clarification, and the proof-of-work spec. Minimal waste, highly structured.

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?

Given zero parameters and an output schema that likely describes the challenge structure, the description is largely complete. The proof-of-work algorithm is specified. It doesn't explain what to do with the notices beyond retrieval or how to use the response in subsequent calls, but that may be covered by the output schema and sibling tool context.

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

Parameters4/5

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

The tool has zero parameters)Skip, so there are no params to describe. Per instructions, with 0 params, baseline is 4. No additional semantic info needed; the description focuses on the output's nature, which is appropriate.

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 clearly states it retrieves processing notices, OCR supplier notices, and a proof-of-challenge work—specific resources with clear intent. It distinguishes itself from analysis and result tools by focusing on requirements, though it doesn't explicitly name sibling tools.

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 mentions that normal analysis requires no additional FINLY approval, providing a when-to-use condition. However, it doesn't explicitly say when to choose this over siblings or mention alternatives directly, leaving some inference needed.

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?