handle-mcp

vis_beholdning

Read-only

Displays your current home inventory—fridge, freezer, and cupboard—with last-updated notes so you can plan meals and shopping lists without buying items you already have.

Instructions

Det I har hjemme (køleskab, fryser, skab), som I sidst har fortalt det. noteret er hvornår hver vare sidst blev opdateret: gamle varer kan være brugt eller for gamle. Brug den til madplaner og indkøbslister, så I ikke køber det, I allerede har.

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": "vis_beholdning"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.37.0Nov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description still adds real behavioral value by explaining the 'noteret' timestamp and warning that old entries may already be consumed or expired, which tells the agent how far to trust the data.

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?

Three short sentences, front-loaded with the core meaning, followed by the timestamp note and the use case. Each sentence contributes, though 'gamle varer kan være brugt eller for gamle' slightly overlaps with the preceding timestamp explanation.

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 zero-parameter, read-only lookup with no output schema, this is close to complete: it says what is returned, how fresh it is, and when to use it. The only gap is that the overall shape of the returned inventory (grouping, fields) is only partially implied via 'noteret'.

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 takes zero parameters, so the baseline is 4. The mention of 'noteret' describes a returned field rather than an input, but it usefully orients the agent to the record's structure given there is no output schema.

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 concrete verb + resource: it shows the household's stock ('Det I har hjemme') broken down by fridge, freezer and cupboard, and clarifies it is the state as last reported. That makes the read-snapshot nature obvious, but it never explicitly distinguishes itself from the sibling 'opdater_beholdning', leaving that inference to the agent.

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?

Usage is stated concretely: use it for meal plans and shopping lists so you avoid buying what is already at home. That is a clear context for invoking the tool, but there is no explicit 'do not use when' guidance and no named alternative for related tasks.

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