handle-mcp

tidligere_ordrer

Read-only

Fetch previous orders or return the items from a specific order ID, helping users identify and repeat past purchases.

Instructions

Tidligere ordrer. Med ordre_id: varerne i den ordre (godt til 'det vi plejer at købe').

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

Input Schema

Name	Required	Default
`antal`	No
`butik`	No	nemlig
`ordre_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Beyond the read-only annotation, the description usefully discloses that the tool's behavior changes from previous orders to the contents of one order when ordre_id is supplied. It remains basic because it says nothing about account or session requirements, ordering or recency of results, empty results, or store-specific behavior.

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?

The text is compact and front-loads the general resource, then immediately presents the conditional mode and a practical example. Its fragmentary style is easy to scan, although it is too terse to cover several invocation-relevant details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An agent can make a basic no-argument call and understands the special ordre_id mode, making the definition minimally usable. However, with no output schema and no parameter descriptions, the omission of ID discovery, antal and butik semantics, result ordering, and expected contents for each mode leaves clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description only compensates for ordre_id by explaining its effect and giving a use case. It does not clarify whether antal limits orders or items, how results are selected, or which values butik accepts beyond the schema's default.

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 identifies the resource as previous orders and adds a useful second mode: supplying ordre_id returns the items in that order. The opening phrase largely restates the tool name and no sibling differentiation is provided, but the overall purpose is clear.

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?

It explicitly conditions the item-level mode on ordre_id and gives the concrete shopping intent 'det vi plejer at købe'. It does not explain the likely workflow of first listing orders to obtain an ID, nor when another sibling tool would be preferable.

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