Skip to main content
Glama
Sign In

Gulvbuddy prisestimat

by dk.gulvbuddy
OverviewDiscussionsAdmin

Prisindeks

prisindeks
Read-onlyIdempotent

Get the current Gulvbuddy price index for wood floors in Denmark, under a Creative Commons Attribution licence, with edition, date and source URLs to cite. Giver Gulvbuddys prisindeks: vejledende priser pr. m² og gennemregnede boliger, med udgave, dato, licens (CC BY 4.0) og adresserne på siden og datafilerne. Ingen input.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prisindeks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
kildeYes
indeksYes
citer_somYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "citer_som": {
+      "type": "string"
+    },
+    "indeks": {
+      "additionalProperties": {},
+      "properties": {
+        "licens": {
+          "additionalProperties": {},
+          "properties": {
+            "navn": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "navn",
+            "url"
+          ],
+          "type": "object"
+        },
+        "navn": {
+          "type": "string"
+        },
+        "prM2": {
+          "items": {
+            "additionalProperties": {},
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "udgave": {
+          "additionalProperties": {},
+          "properties": {
+            "dato": {
+              "type": "string"
+            },
+            "id": {
+              "type": "string"
+            },
+            "navn": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "dato",
+            "navn"
+          ],
+          "type": "object"
+        },
+        "url": {
+          "type": "string"
+        },
+        "valuta": {
+          "const": "DKK",
+          "type": "string"
+        }
+      },
+      "required": [
+        "navn",
+        "url",
+        "udgave",
+        "licens",
+        "valuta",
+        "prM2"
+      ],
+      "type": "object"
+    },
+    "kilde": {
+      "additionalProperties": {},
+      "properties": {
+        "csv": {
+          "type": "string"
+        },
+        "json": {
+          "type": "string"
+        },
+        "side": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "side",
+        "json",
+        "csv"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "citer_som",
+    "kilde",
+    "indeks"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds behavior the annotations cannot: the data is licensed CC BY 4.0, the agent must cite the page and data-file URLs, and the response includes the edition/date for citation. That licensing/attribution obligation is the genuinely valuable addition.

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 content is front-loaded and each language version is tight, but the same information is delivered twice in English and Danish, roughly doubling the length without adding meaning. A single bilingual-savvy sentence would have earned a higher score.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarises them (price per m², worked-through housing examples, edition, date, licence, URLs). Together with the attribution requirement, this covers what an agent needs to call an input-free index tool correctly.

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?

The tool has zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly states 'Ingen input', confirming to the agent that no arguments are expected.

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 names a specific verb and resource: the current Gulvbuddy price index for wood floors in Denmark, and states the currency/source framing (edition, date, source URLs). It is clearly distinguishable from siblings such as forklar_prisen and ydelser, though it does not name any 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 Guidelines3/5

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

The description tells the agent that no input is needed ('Ingen input' / 'Giver... med udgave, dato...') and that attribution is required when citing, which is implied usage guidance. It does not state when to prefer this over forklar_prisen or ydelser, nor any exclusions.

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

All Gulvbuddy prisestimat toolsInspect
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