Skip to main content
Glama

Remont — renovation planner

Open saved plan

open_plan
Read-only

Opens a saved plan with ticked tasks. Ticks keep being saved on the server.

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

Input Schema

NameRequiredDescriptionDefault
plan_idYes
user_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description says "Ticks keep being saved on the server," which implies persistence or mutation caused by opening the plan. This conflicts with the read-only annotation and leaves the tool's actual side effects unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded, but the second sentence is confusing and introduces the annotation contradiction rather than useful behavioral context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, 0% parameter coverage, and a description that contradicts the read-only annotation, an agent lacks the information needed to call this tool confidently or understand its effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain either required parameter. "Saved plan" weakly implies plan_id, but user_code is entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb ("Opens") and resource ("saved plan") but adds an unclear qualifier, "with ticked tasks," and does not distinguish it from siblings like get_plan or open_questionnaire. An agent can form a rough idea of purpose but not a precise one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as get_plan or open_questionnaire, and no preconditions or exclusions are mentioned.

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