Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Onboarding Status

get_onboarding_status
Read-only

Track current-year LMNP onboarding progress, including property setup, income/expense entry, depreciation setup, year-end closing, and PDF tax package generation.

Instructions

Retourne l'état d'avancement de l'onboarding LMNP de l'utilisateur pour l'année courante : création du bien, saisie des recettes et charges, configuration des amortissements, clôture de l'exercice et génération de la liasse fiscale PDF.

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

Input Schema

NameRequiredDescriptionDefault
yearNoAnnée fiscale (défaut : année précédente)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / year / description
      Added value: +"Année fiscale (défaut : année précédente)"
  2. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's added value is the scope: a per-step progress breakdown across five onboarding stages. It does not say whether partially completed steps are reported, how completion is determined, or what the returned structure looks like, so the behavioral gain is moderate rather than rich.

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?

A single front-loaded sentence with the resource and scope stated first, followed by an enumeration that earns its length by defining the covered stages. No filler or repeated information.

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?

For a read-only, zero-required-parameter progress tool with no output schema, the enumeration of tracked stages gives an agent enough to decide relevance and interpret a result. The only real gap is the unresolved current-year versus default-previous-year ambiguity.

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%, so the single 'year' parameter is already documented, and the description adds nothing about its semantics. It also creates a mild inconsistency: the description pins the status to 'l'année courante' while the schema defaults 'year' to the previous fiscal year, which could confuse an agent about what it gets when omitting the parameter.

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 a specific verb and resource ('Retourne l'état d'avancement de l'onboarding LMNP') and enumerates the five steps whose progress is reported, so an agent knows this is an aggregate progress read, not a single-entity fetch. It does not explicitly contrast itself with aggregate siblings like get_dashboard_summary, which keeps it out of 5 territory.

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 only implied: an agent can infer it should call this to check onboarding completion, but there is no statement of when to prefer it over get_dashboard_summary or the individual get_property/get_income/get_expense tools. No exclusions or prerequisites are given.

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