Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Dashboard Summary

get_dashboard_summary
Read-only

Returns an aggregated dashboard for a selected year or the current year, showing property and loan counts, total income and expenses, tax result, and breakdowns by platform and category.

Instructions

Retourne un tableau de bord agrégé pour l'utilisateur : nombre de biens et emprunts, recettes et charges totales pour l'année demandée (défaut : année en cours), résultat fiscal si l'exercice existe, et répartition des recettes par plateforme et des charges par catégorie.

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_dashboard_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoAnnée à analyser, ex: 2024 (optionnel — défaut : année en cours)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / year / description
      Added value: +"Année à analyser, ex: 2024 (optionnel — défaut : année en cours)"
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's marginal burden is low. It does add useful behavioral detail beyond the annotations — the default year and the fact that 'résultat fiscal' only appears if the fiscal exercise exists — but says nothing about volume, empty-account behavior, or performance.

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?

A single well-formed sentence that front-loads the aggregated nature and then lists contents in a logical order. No filler, no repetition of the title.

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, the description carries the return-value burden and does so by enumerating every section of the dashboard, including a conditional one. Minor gap: it doesn't say whether sections are omitted or empty when the user has no properties/loans.

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?

Schema coverage is 100% and the schema already documents 'year' with the same default and an example, so the description mostly restates it. Baseline 3 applies; no additional format, range, or edge-case semantics are contributed.

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?

States a specific verb and resource ('Retourne un tableau de bord agrégé') and enumerates exactly what is aggregated: property/loan counts, income and expenses, tax result, and per-platform/per-category breakdowns. This clearly separates it from single-record siblings like get_income or get_expense, though no sibling is named explicitly.

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 by the aggregated, whole-portfolio scope: an agent can infer 'call this for an overview, call get_income/get_expense for detail.' However, there is no explicit when-to-use statement, no exclusion, and no named alternative.

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