Gulvbuddy prisestimat

Valgmuligheder

valgmuligheder

Read-onlyIdempotent

List the valid choices, with ids and Danish names, for the estimate and booking tools. Giver gyldige id'er med dansk navn for hvert valg i estimaterne og bookinglinket. Input: spor.

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": {
      "spor": "<spor>"
    },
    "name": "valgmuligheder"
  }
}

Input Schema

Name	Required	Description	Default
`spor`	Yes	Sporet: nyt_gulv (nyt trægulv) eller slibning (afslibning af eksisterende gulv).

Output Schema

Name	Required	Description	Default
`spor`	Yes
`felter`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

addedInput schema / properties / spor / description

Added value: +"Sporet: nyt_gulv (nyt trægulv) eller slibning (afslibning af eksisterende gulv)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "felter": {
+      "additionalProperties": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "beskrivelse": {
+              "type": "string"
+            },
+            "id": {
+              "type": "string"
+            },
+            "moenster": {
+              "type": "string"
+            },
+            "navn": {
+              "type": "string"
+            },
+            "traesort": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "navn"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "spor": {
+      "enum": [
+        "nyt_gulv",
+        "slibning"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "spor",
+    "felter"
+  ],
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that results carry ids and Danish names, which is marginal given an output schema exists. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, but the Danish sentence restates the same content verbatim and the dangling 'Input: spor.' fragment adds no information. Two of the four sentences do not earn their place.

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 one-parameter, read-only enum lookup with rich annotations and an output schema, the description is sufficient to call it correctly. The remaining gap is failing to name the concrete sibling tools whose ids it supplies.

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 description coverage is 100% and the single 'spor' parameter already has an enum with per-value descriptions, so the schema carries the load. The trailing 'Input: spor.' adds nothing beyond it, but with one fully-documented enum parameter the baseline is met.

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 gives a specific verb ('List') and resource ('the valid choices, with ids and Danish names') plus its consumer scope ('for the estimate and booking tools'), so an agent can tell it is a lookup feeding estimer_* and start_booking. It stops short of naming those sibling tools explicitly, which keeps it from a 5.

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?

Use is only implied: the mention of 'estimate and booking tools' hints the agent should fetch ids before calling them, but there is no explicit 'call this before estimer_slibning/estimer_traegulv/start_booking' or any when-not guidance. No alternative sibling is named or excluded.

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?