Skip to main content
Glama

Binyan.im · בניינים

Debt reminders

analyze_debts_and_generate_reminders
Read-only

Analyze apartment debt. Monthly dues are due on the building's dues day (duesDueDay in building settings, 10 unless changed). asOfDate defaults to today in the building's time zone (timezone in building settings) and splits overdue from dueSoon. The response echoes timezone and dueDay. Reminders target overdue apartments unless includeDueSoon is true. The overdue total matches generate_financial_report outstanding and the dashboard pending collections.

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>"
    },
    "name": "analyze_debts_and_generate_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfDateNo
buildingIdYes
includeDueSoonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: the dues day default of 10, timezone-based asOfDate defaulting, the overdue/dueSoon split, the echoed timezone and dueDay fields, and consistency with other reporting surfaces.

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?

Six short sentences with no filler, and the core behavior (dues day, asOfDate default, overdue/dueSoon split) is front-loaded. The final consistency sentence is useful but sits slightly awkwardly at the end rather than being folded into the behavior statement.

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?

With no output schema and no schema parameter descriptions, the definition has to explain both semantics and return shape, and it does name what the response echoes (timezone, dueDay) and what totals reconcile against. What is missing is any description of the actual reminder payload or per-apartment output fields, which an agent would need to act on the results.

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?

Schema coverage is 0%, so the description must carry parameter meaning and it mostly does: asOfDate is explained as defaulting to today in the building's timezone and as the cutoff that splits overdue from dueSoon, and includeDueSoon is explained as broadening reminder targets. buildingId's building-scoped meaning is only implied by "apartment debt" and "building settings" references.

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?

"Analyze apartment debt" plus the reminder framing tells the agent this computes per-apartment debt status and produces reminder targets. It is a specific verb+resource, though "analyze" alone is broad and the reminder-generation aspect is only clarified by later sentences rather than the opening line.

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?

It gives the key behavioral lever ("Reminders target overdue apartments unless includeDueSoon is true") and links results to generate_financial_report and the dashboard, which implies when this tool is the right source. However, it never states when NOT to use it or how it differs in scope from those referenced tools.

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