Skip to main content
Glama

Remont — renovation planner

Mark materials bought

mark_bought

Marks plan materials as bought (or un-marks them) when the user says in the chat that they bought something. The plan widget has the same 🛒 tick per material. Bought lines stay in the estimate; the plan shows «bought» and «left to buy». Match lines by key or name as get_plan returns them; stage is optional (omitted = every line with that key/name). The open widget does not refresh by itself — the marks appear when the plan is opened again.

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>",
      "items": "<items>"
    },
    "name": "mark_bought"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
boughtNotrue = bought (default), false = un-mark
view_idYesview_id of the plan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=false, and the description stays consistent with that while adding real behavioral facts: bought lines stay in the estimate, the plan displays «bought»/«left to buy», and the open widget will not refresh by itself. That stale-UI caveat is non-obvious and not derivable from annotations. It does not cover permission requirements or failure behavior for unmatched lines.

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?

Four sentences, front-loaded with the action, then trigger, then line-matching, then the refresh caveat. No filler and nothing repeated from structured fields.

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 mutation tool with no output schema and moderate complexity, this covers the action, trigger, line targeting, side effects on the estimate, and the UI refresh limitation. Only error handling for unmatched keys or permissions is absent, which is a minor gap.

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

Parameters4/5

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

Schema coverage is 67% and the description adds meaning where the schema is thin: key/name matching rules ("as get_plan returns them") and the semantics of omitting stage (applies to every line with that key/name). The bought default is already in the schema, so no credit there, but the matching semantics are a genuine addition.

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

Purpose5/5

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

Specific verb plus resource with toggle semantics spelled out ("Marks plan materials as bought (or un-marks them)"), and it ties identity to what get_plan returns so the agent knows which lines are addressable. It also names the equivalent manual affordance (the 🛒 tick in the plan widget), which anchors the concept immediately.

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?

Gives a concrete trigger ("when the user says in the chat that they bought something") and clarifies the optional-parameter case ("omitted = every line with that key/name"). It stops short of naming a sibling alternative for adjacent cases, but the when-to-use condition is unambiguous.

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