Skip to main content
Glama

Remont — renovation planner

Get work order

get_work_order
Read-only

Renovation stages in the right order with tasks, drying times and where a specialist is needed.

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": {
      "works": "<works>"
    },
    "name": "get_work_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
worksYesWhich works the renovation includes
ui_localeNoLanguage of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 some content context beyond that (stages come ordered, include tasks, drying times and specialist requirements), but says nothing about how the works list shapes the output or how results are grouped.

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?

A single short sentence with no filler, and the informative content (ordering, tasks, drying times, specialists) comes first. It loses a point for being a fragment with no action verb, which weakens front-loading of what the tool actually does.

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?

With no output schema, the description carries the burden of explaining return values, and it only partially does so. It never explains how the required works array affects the result or how stages relate to specialist tasks, so an agent can call the tool but cannot predict the shape of what it gets back.

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 description coverage is 100%, so both parameters are documented in the schema, and the baseline is 3. The description adds no meaning on top of that: it never mentions the works filter or the ui_locale language requirement.

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 names the resource returned ("renovation stages... with tasks, drying times and where a specialist is needed"), but it is a noun phrase with no verb and never ties itself to the tool name or to the required "works" input, so an agent must infer that this returns an ordered work sequence for the requested works. It also does not distinguish itself from plausible siblings such as show_renovation_plan or get_plan.

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 when-to-use guidance, no exclusions, and no reference to any alternative tool. The agent is left to guess whether this is a sequencing helper or a plan viewer based on the name alone.

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