Gulvbuddy prisestimat

Hent guide

hent_guide

Read-onlyIdempotent

Get a full Gulvbuddy guide as markdown, with its canonical URL. Giver hele guiden som markdown med de samme tal som siden, og adressen på siden. Input: guidens slug, som står i adressen på guiden.

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": {
      "slug": "<slug>"
    },
    "name": "hent_guide"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Guidens slug: den sidste del af guidens adresse på gulvbuddy.dk.

Output Schema

Name	Required	Description	Default
`url`	Yes
`slug`	Yes
`titel`	Yes
`markdown`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

addedInput schema / properties / slug / description

Added value: +"Guidens slug: den sidste del af guidens adresse på gulvbuddy.dk."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "markdown": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "titel": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "titel",
+    "url",
+    "markdown"
+  ],
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

B3.4/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 still adds real value beyond that by disclosing the output is a complete guide rendered as markdown, includes the same figures as the live page, and carries the canonical URL.

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?

Short and front-loaded with the outcome, which is good, but the entire content is duplicated in Danish and English, so three of the sentences add no new information. The bilingual mirroring costs efficiency without adding agent-relevant detail.

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 tool with full annotation coverage and an output schema, the description supplies what is missing: the output format and the URL fidelity guarantee. Only failure behavior for an invalid slug is unaddressed, which is minor at this complexity.

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 single slug parameter is already well documented in the schema as the last segment of the guide URL. The description's 'slug, som står i adressen' restates that same fact rather than adding format, length or validity details.

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 (fetch a Gulvbuddy guide) and adds the return format (markdown plus canonical URL). It is clearly distinguishable from every sibling, which are pricing, booking and coverage tools, though it never names an alternative explicitly.

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?

The description tells the agent how to call the tool (supply the slug from the guide's URL) but never says when to reach for it versus siblings like soeg_svar, prisindeks or ydelser, nor when not to. Usage is only inferrable from the name.

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?