Skip to main content
Glama

Remont — renovation planner

List saved plans

list_plans
Read-only

List of the user's saved plans by their personal code. Each plan has title, saved_at and (for plans saved after this field was added) country, currency, area_m2, rooms, stages, total_min/total_max (grand total incl. 10% reserve at save time). Older plans may lack these fields.

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": {
      "user_code": "<user_code>"
    },
    "name": "list_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_codeYesPersonal code

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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the per-plan field set, the meaning of total_min/total_max (grand total including a 10% reserve computed at save time), and the caveat that plans saved before a schema addition may omit fields. What it omits is ordering, pagination, and behavior for an unknown user_code.

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?

Two sentences, front-loaded with what the tool returns, then the legacy-data caveat. The field enumeration is long but earns its place because no output schema exists.

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 well by listing plan fields and explaining the reserve-inclusive totals. Remaining gaps are operational rather than structural: ordering, result limits, and empty-result behavior are unstated.

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% for the single required parameter, and 'by their personal code' only restates the schema's 'Personal code' description. With the schema doing the heavy lifting, the baseline 3 applies; no format, validation, or lookup-failure semantics are added.

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 (list) and resource (user's saved plans) scoped by personal code, which distinguishes it from get_plan and open_plan by name alone. It stops short of naming a sibling to contrast with, so it lands just under a 5.

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 scoping phrase 'by their personal code' implies a browse/discovery use case, and the mention of older plans lacking fields hints at a survey-then-inspect workflow. However, it never says when to prefer this over get_plan for a single plan, nor states any prerequisites or exclusions.

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