Skip to main content
Glama

Remont — renovation planner

Plan button task

plan_task

Call FIRST when a user message comes from a plan button: it contains [view_id: …] and asks (in the user's language) to find missing prices, refresh all prices, find options for an item, check compatibility or save the plan. Returns the item list and the exact steps.

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": {
      "view_id": "<view_id>",
      "action": "<action>"
    },
    "name": "plan_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNoFor options: the item name from the message
actionYes
view_idYesview_id from the message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it states the return payload ('the item list and the exact steps'), which hints that the tool resolves and plans rather than blindly executing. It does not state whether the underlying change is applied immediately or requires a follow-up call, which for a non-read-only tool is a meaningful remaining gap.

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?

One dense sentence, front-loaded with the activation rule ('Call FIRST when…') followed by the detection signal and the supported intents. No filler and nothing that repeats the schema verbatim.

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, stating that it returns the item list and the exact steps is the right compensating detail, and the intent list covers the schema enum well. The remaining gap is the unmentioned 'recalc' action and the unanswered question of whether dispatching here actually applies changes.

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 67% and the enum is documented in the schema, so the baseline is 3. The prose does map most intents to user-facing requests ('find missing prices, refresh all prices, find options for an item, check compatibility or save the plan'), which helps pick an action value. However, the 'recalc' enum member is never mentioned and the 'item' parameter's conditional relevance is only partly echoed ('find options for an item'), so it adds only marginal meaning.

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 names a specific job: it is the entry point for user messages originating from a plan button that carry a [view_id: …] token, and it enumerates the intent families it handles (missing prices, refresh, options, compatibility, save). That distinguishes it from the specific executors in the sibling list such as refresh_plan_prices and save_plan. It stops short of a crisp one-line 'what it does' statement, since it never says whether it performs the action or only routes it.

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

Usage Guidelines4/5

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

It gives an explicit, checkable trigger ('Call FIRST when a user message comes from a plan button: it contains [view_id: …]') and a sequencing instruction relative to other tools. It does not name a when-not condition or point at a specific alternative for messages without a view_id, but the trigger signature is precise enough that misuse is unlikely.

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