Gulvbuddy prisestimat

Forklar prisen

forklar_prisen

Read-onlyIdempotent

Explain how Gulvbuddy's price works, in approved wording. Giver en godkendt forklaring på ét emne: hvad_flytter_prisen, undergulv, spild, fra_estimat_til_fast_pris, varighed, slibning_hvad_er_med. Forklaringen er uden tal og procenter.

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": {
      "emne": "<emne>"
    },
    "name": "forklar_prisen"
  }
}

Input Schema

Name	Required	Description	Default
`emne`	Yes	Emnet der forklares: hvad_flytter_prisen, undergulv, spild, fra_estimat_til_fast_pris, varighed, slibning_hvad_er_med.

Output Schema

Name	Required	Description	Default
`emne`	Yes
`afsnit`	Yes
`punkter`	No
`laes_mere`	Yes
`overskrift`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

addedInput schema / properties / emne / description

Added value: +"Emnet der forklares: hvad_flytter_prisen, undergulv, spild, fra_estimat_til_fast_pris, varighed, slibning_hvad_er_med."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "afsnit": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "emne": {
+      "type": "string"
+    },
+    "laes_mere": {
+      "type": "string"
+    },
+    "overskrift": {
+      "type": "string"
+    },
+    "punkter": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "navn": {
+            "type": "string"
+          },
+          "tekst": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "navn",
+          "tekst"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "emne",
+    "overskrift",
+    "afsnit",
+    "laes_mere"
+  ],
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world), so what matters is added behavior — and the description supplies it: the answer is drawn from approved/approved-wording text and deliberately contains no numbers or percentages, which tells the agent not to expect concrete figures here. It stops short of describing the answer's structure or length, which is partly covered by 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?

Two compact sentences, front-loaded with the purpose and followed by the topic scope and the no-numbers rule. The enumeration of all six enum values duplicates the schema, and the mixed English/Danish phrasing makes it slightly less scannable than it could be.

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 single-parameter, read-only explanation lookup with a full output schema and complete annotations, the description covers what the tool does, its scope, and its key output constraint. Only the routing against price-related siblings (prisindeks, ydelser, valgmuligheder) is left unstated.

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 100% and the enum values are fully documented in the schema, so the description's restatement of the six topics adds no new meaning. The only semantic addition is the implicit constraint of exactly one topic per call, which is already enforced by the single required parameter.

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 states a concrete verb and resource: give an approved explanation of how Gulvbuddy's pricing works, limited to one topic from a fixed list. It implicitly separates it from data-oriented siblings like prisindeks by stressing "godkendt forklaring" and "uden tal og procenter", but never names a sibling explicitly.

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

Usage Guidelines3/5

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

"Giver en godkendt forklaring på ét emne" implies one call per topic and implies this is the tool for qualitative price explanation, but there is no explicit when-to-use vs. when-not guidance and no reference to the other price-related siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gulvbuddy prisestimat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?