Skip to main content
Glama

Maison et entretiens

dandori_list_home
Read-onlyIdempotent

Équipements de la maison (garanties comprises) et leurs tâches d'entretien, avec leurs ID ; avec logs, l'historique des entretiens faits

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

Input Schema

NameRequiredDescriptionDefault
logsNotrue : ajoute les entretiens faits, les plus récents d'abord (avec leurs ID)
roomNoFiltrer les équipements par pièce
categoryNoFiltrer les équipements
upcoming_daysNoSeulement les entretiens dus dans ce nombre de jours (retards compris)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: that warranties are included, that IDs are returned (enabling follow-up calls), and that logs are ordered most-recent-first. It says nothing about result volume, limits, or pagination, which keeps it from a higher score.

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 compact sentence that front-loads the primary content (equipment and maintenance tasks with IDs) before the optional logs behavior. The parenthetical 'garanties comprises' is informative rather than wasteful; no filler sentences are present.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so adequately: equipment, warranties, maintenance tasks, IDs, and optionally history. Given the annotations cover safety and the schema covers all parameters, an agent has enough to call this correctly, with only result volume left unspecified.

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 description coverage is 100%, so each parameter is already documented in the schema, including the enum values for category and the minimum for upcoming_days. The description only restates the logs behavior at a high level and adds no format or interaction details beyond the schema, making the baseline 3 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 states a specific verb-and-resource pairing: it returns home equipment (including warranties) together with their maintenance tasks and IDs, and optionally the maintenance history. The resource is clearly distinct from the other list_* siblings, so an agent can identify the domain without opening the schema, though it never explicitly names a contrasting sibling.

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?

The clause 'avec logs, l'historique des entretiens faits' implies when the history variant is relevant, and the parameters imply filtering contexts. However, there is no explicit statement of when to choose this tool over related ones (e.g. task or routine listings) and no prerequisites or exclusions are given.

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