Skip to main content
Glama

Gulvbuddy prisestimat

Estimer gulvafslibning

estimer_slibning
Read-onlyIdempotent

Estimate the price of sanding and refinishing an existing wood floor in Denmark (DKK incl. VAT). Giver et vejledende prisestimat for gulvafslibning inkl. moms, som et spænd fra og til. Et estimat er ikke et tilbud; den faste pris kommer efter opmåling. Felter der udelades, indgår som et spænd over alle valgmuligheder.

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": {
      "m2": "<m2>"
    },
    "name": "estimer_slibning"
  }
}

Input Schema

NameRequiredDescriptionDefault
m2YesGulvets areal i kvadratmeter (m²).
slidNoGulvets slidtage (wear): let: Lidt slidt, middel: En del slid, kraftig: Meget slidt.
farveNoFarvevalg på det slebne gulv (colour). Hvilke farver der findes, følger træsorten. varm: Varm, neutral: Neutral, mork: Mørk, hvidneutral: Hvid/neutral, hvid: Hvid, neutralmat: Neutral.
omfangNoHvor meget der slibes (scope): hele: Hele boligen, rum: Udvalgte rum.
traesortNoGulvets træsort og udseende (wood type): fyr: Fyrretræ, fyr_olieret: Fyrretræ (olieret), bog: Bøg stavparket, skovfyr: Skovfyr, andet: Andet træ.
behandlingNoOverfladebehandling efter slibning (finish): olie: Olie, lak: Lak, lud: Lud + sæbe.
slebet_foerNoOm gulvet er slebet før (previously sanded): nej: Nej, en_gang: Ja, én gang, flere: Ja, flere gange, ved_ikke: Det ved jeg ikke.

Output Schema

NameRequiredDescriptionDefault
sporYes
typeYes
beskedYes
metodeYes
areal_m2Yes
varighedYes
forbeholdYes
uoplyste_valgYes
pris_inkl_momsYes
konfigurator_urlYes
uoplyste_valg_tekstYes
minimumspris_slaar_tilYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / behandling / description
      Added value: +"Overfladebehandling efter slibning (finish): olie: Olie, lak: Lak, lud: Lud + sæbe."
    • addedInput schema / properties / farve / description
      Added value: +"Farvevalg på det slebne gulv (colour). Hvilke farver der findes, følger træsorten. varm: Varm, neutral: Neutral, mork: Mørk, hvidneutral: Hvid/neutral, hvid: Hvid, neutralmat: Neutral."
    • addedInput schema / properties / farve / enum
      Added value: +[
      +  "varm",
      +  "neutral",
      +  "mork",
      +  "hvidneutral",
      +  "hvid",
      +  "neutralmat"
      +]
    • removedInput schema / properties / farve / pattern
      Removed value: -"^[a-z0-9_]{1,24}$"
    • addedInput schema / properties / m2 / description
      Added value: +"Gulvets areal i kvadratmeter (m²)."
    • addedInput schema / properties / omfang / description
      Added value: +"Hvor meget der slibes (scope): hele: Hele boligen, rum: Udvalgte rum."
    • addedInput schema / properties / slebet_foer / description
      Added value: +"Om gulvet er slebet før (previously sanded): nej: Nej, en_gang: Ja, én gang, flere: Ja, flere gange, ved_ikke: Det ved jeg ikke."
    • addedInput schema / properties / slid / description
      Added value: +"Gulvets slidtage (wear): let: Lidt slidt, middel: En del slid, kraftig: Meget slidt."
    • addedInput schema / properties / traesort / description
      Added value: +"Gulvets træsort og udseende (wood type): fyr: Fyrretræ, fyr_olieret: Fyrretræ (olieret), bog: Bøg stavparket, skovfyr: Skovfyr, andet: Andet træ."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "areal_m2": {
      +      "type": "number"
      +    },
      +    "besked": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "forbehold": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "konfigurator_url": {
      +      "type": "string"
      +    },
      +    "metode": {
      +      "type": "string"
      +    },
      +    "minimumspris_slaar_til": {
      +      "type": "boolean"
      +    },
      +    "pris_inkl_moms": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "fra": {
      +              "type": "number"
      +            },
      +            "til": {
      +              "type": "number"
      +            },
      +            "valuta": {
      +              "const": "DKK",
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "fra",
      +            "til",
      +            "valuta"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "spor": {
      +      "const": "slibning",
      +      "type": "string"
      +    },
      +    "type": {
      +      "const": "estimat",
      +      "type": "string"
      +    },
      +    "uoplyste_valg": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "behandling": {
      +            "type": "string"
      +          },
      +          "felt": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "felt",
      +          "behandling"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "uoplyste_valg_tekst": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "varighed": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "dage_fra": {
      +              "type": "number"
      +            },
      +            "dage_til": {
      +              "type": "number"
      +            },
      +            "tekst": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "dage_fra",
      +            "dage_til",
      +            "tekst"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    }
      +  },
      +  "required": [
      +    "type",
      +    "spor",
      +    "areal_m2",
      +    "pris_inkl_moms",
      +    "besked",
      +    "minimumspris_slaar_til",
      +    "varighed",
      +    "uoplyste_valg",
      +    "uoplyste_valg_tekst",
      +    "forbehold",
      +    "metode",
      +    "konfigurator_url"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: output is a DKK range including VAT, the estimate is explicitly non-binding, and omission of optional fields widens the range across all choices. Rate limits, precision caveats and the shape of the returned span are left to the output schema.

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?

Four short sentences, front-loaded with what is being priced and in which currency, followed by the estimate-vs-quote caveat and the omission rule. The Danish sentence largely restates the English one, which is minor redundancy rather than a clarity problem.

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

Completeness5/5

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

For a seven-parameter, fully enum-documented pricing tool with an output schema, the description covers what an agent needs: what is priced, currency and VAT basis, that the answer is a range, that it is non-binding, and how omitted fields are handled. Return-value structure is correctly left to the output schema.

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 100% with enum descriptions on all six optional fields, so the baseline is 3. The description adds genuinely new meaning: fields that are omitted are priced as a span across all available options, which tells the agent how partial input changes the result rather than just what each field is. It does not, however, explain how the required m2 value interacts with the price band.

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?

States a specific verb and resource ('Estimate the price of sanding and refinishing an existing wood floor'), plus market and currency (Denmark, DKK incl. VAT), which lets an agent tell it apart from a sibling like estimer_traegulv. It never names that sibling explicitly, so differentiation is inferred from 'existing' rather than stated.

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 clear situational context: the result is a guiding estimate span, not a binding quote, and the fixed price arrives after on-site measurement. It does not say when to prefer a sibling tool or what to do when the floor is new rather than existing, so no explicit alternative routing is provided.

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