Skip to main content
Glama

Binyan.im · בניינים

Financial report

generate_financial_report
Read-only

Generate a financial report for a building. summary.outstanding is overdue debt as of endDate, from the same calculation as analyze_debts_and_generate_reminders. Monthly dues are due on the building's dues day (duesDueDay in building settings, 10 unless changed), so the current month is dueSoon until that day has passed. Dates follow the building's time zone.

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": {
      "buildingId": "<buildingId>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "generate_financial_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYes
startDateYes
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare it a safe read (readOnlyHint=true, openWorldHint=false), and the description adds real domain context beyond that: what summary.outstanding means, that it shares a calculation with analyze_debts_and_generate_reminders, how dueSoon is determined using duesDueDay with a default of 10, and that dates follow the building's time zone. It does not describe report breadth or size, but the semantics disclosed are substantive.

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?

The purpose is front-loaded in one short sentence, followed by tightly packed clarifying clauses with no filler. The only inefficiency is that field names like summary.outstanding and dueSoon appear without setup, so the reader must parse a dotted path mid-sentence.

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

Completeness3/5

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

There is no output schema, so the description is the only source of return-shape information, and it defines just two concepts (summary.outstanding and dueSoon) while implying a larger report structure that is never outlined. Combined with the unexplained startDate, the definition is workable but not complete for a three-required-parameter report generator.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it partially does: endDate is pinned to the outstanding-debt snapshot, dates are declared as YYYY-MM-DD-style day-granularity values resolved in the building's time zone, and buildingId is implied by 'for a building.' startDate is never explained, and the time-zone rule is not tied to a specific parameter, leaving a clear gap.

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 first sentence states a specific verb and resource ('Generate a financial report for a building'), which is unambiguous on its own. It does not explicitly contrast with list/expense siblings, but it does name analyze_debts_and_generate_reminders as the source of the same calculation, which anchors it relative to at least one alternative.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the reporting tool for a building, and the reference to analyze_debts_and_generate_reminders hints at a relationship. However, there is no explicit 'use this when' rule, no exclusion of alternatives, and no guidance on choosing between this and the analysis tool it cites.

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