handle-mcp

soeg_varer

Read-only

Search products in a single Nemlig or Bilka store to return price, unit price, offers, and stock, with optional price-first sorting when cost matters.

Instructions

Søg efter varer i én butik (nemlig eller bilka). Giver pris, enhedspris, tilbud og lager. Butikken sorterer efter popularitet, så de billigste varer er tit ikke i toppen. Sæt billigst_foerst=True for at gennemsøge flere hits og ugens tilbud og få de relevante varer på lager sorteret efter det billigste køb. Står der en mængde i teksten ("500 g hakket oksekød"), sorteres efter prisen for at dække den. Brug det, når prisen betyder noget, og prøv flere søgetekster (fx "kyllingebryst øko", "kyllingeinderfilet"), før du vælger.

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": {
      "tekst": "<tekst>"
    },
    "name": "soeg_varer"
  }
}

Input Schema

Name	Required	Default
`antal`	No
`butik`	No	nemlig
`tekst`	Yes
`oekologisk`	No
`billigst_foerst`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.37.0Nov 11, 2026

addedInput schema / properties / billigst_foerst

Added value: +{
+  "default": false,
+  "title": "Billigst Foerst",
+  "type": "boolean"
+}

addedInput schema / properties / oekologisk

Added value: +{
+  "default": false,
+  "title": "Oekologisk",
+  "type": "boolean"
+}

First observedv0.1.0Nov 4, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral detail beyond them — results are sorted by popularity so cheapest items aren't at the top, and billigst_foerst widens the search to more hits and weekly offers and re-sorts by cheapest purchasable in-stock item. It also explains the quantity-parsing behavior ('500 g hakket oksekød' triggers sorting by price for that amount), which materially changes how an agent should call it.

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?

Front-loads purpose and return values in the first sentence, then behavior, then usage advice. Dense but every sentence contributes; the nested quote examples are slightly verbose but illustrative.

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?

With no output schema, stating that results include price, unit price, offer and stock is necessary and present. For a five-parameter tool with zero schema documentation, the unexplained antal and oekologisk parameters are the main remaining gap; safety is covered by annotations.

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 description coverage is 0%, so the description carries the burden. It explains billigst_foerst well and implies the store options for butik, and it hints that quantity text in 'tekst' is parsed, but antal and oekologisk are left completely unexplained, so only part of the gap is closed.

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?

Names a specific verb and resource ('Søg efter varer') and constrains scope to one store (nemlig or bilka), plus states what comes back: price, unit price, offer and stock. It doesn't explicitly contrast with siblings, but the siblings listed (recipes, basket, plans) are in clearly different domains, so an agent can place it without confusion.

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 a clear trigger ('Brug det, når prisen betyder noget') and prescribes a strategy: try several search terms before choosing. There is no explicit when-NOT-to-use or named alternative, so it stops short of full routing guidance.

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