Skip to main content
Glama

Remont — renovation planner

Refresh plan prices

refresh_plan_prices
Read-only

Internal: the open plan calls it to pull prices you saved to the catalog after showing the plan. You do not need to call it.

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

Input Schema

NameRequiredDescriptionDefault
laborNo
toolsNo
countryNo
view_idNo
materialsNo
refresh_sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/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 new context beyond them: the tool is invoked internally by the open plan, runs after the plan is shown, and pulls prices from the user's saved catalog rather than a live external source. What it doesn't say is what a caller would receive if invoked manually.

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 short sentences with no filler, and the decisive instruction ('You do not need to call it') is easy to find. The phrasing is grammatically tangled ('the open plan calls it to pull prices you saved to the catalog after showing the plan'), which costs a little clarity.

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

Completeness3/5

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

For a tool the agent is told not to invoke, exhaustive parameter documentation matters less, so the definition is arguably sufficient for its stated role. Still, with six undocumented parameters, no output schema, and no note on what happens on manual invocation, it leaves real gaps if an agent ever does call it.

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

Parameters2/5

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

With six parameters and 0% schema description coverage, the description carries the full burden and does not meet it — labor, tools, materials, country, view_id, and refresh_since are never mentioned. The only faint signal is that it deals with catalog prices, which loosely maps to materials/labor, but there is no explanation of shape, units, or the meaning of refresh_since.

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 identifies the resource (plan prices) and the source (prices saved to the catalog), and labels the tool as internal plumbing invoked by open_plan. However, the verb is buried in an awkward clause ('pull prices you saved... after showing the plan') rather than stated as a direct action, so an agent must parse it to understand that this refreshes plan prices from the catalog.

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 unusually explicit exclusion for an agent-facing definition: 'You do not need to call it,' plus names the actual caller (the open plan). That is a clear when-not-to-use signal. It stops short of 5 because no alternative tool is named for the case where an agent wants catalog prices — a sibling like find_cached_prices would have completed the routing.

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