Skip to main content
Glama
Robert-SD

appie-mcp

by Robert-SD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Albert Heijn Weekly Bonus Offers

ah_get_bonus_offers
Read-only

Browse active Albert Heijn Bonus folder discounts and promotions with validity windows; use page and limit to view offers beyond the first page.

Instructions

Browse active national Bonus folder discounts, promotions (e.g. 1+1 gratis, 2e halve prijs), and validity windows. The folder is far larger than one page: walk page with limit to see more of it. Cached for up to 30 minutes.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 0)
limitNoOffers per page (default 30, max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 30,
+  "description": "Offers per page (default 30, max 100)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 0,
+  "description": "Page number (default 0)",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint already covers the safety profile, so the description's added value is staleness and volume: it discloses a 30-minute cache and warns that the folder spans far more than one page. That is real behavioral context beyond annotations. It stops short of describing the response shape or whether pages are stable/ordered while cached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero filler, front-loading what the tool returns (discounts, promotion types, validity) before pagination mechanics and caching. Each sentence contributes a distinct fact.

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 simple two-param read tool with no output schema, the description covers scope, promotion examples, pagination strategy and cache freshness. The only remaining gap is what an offer record actually contains, which an agent must discover by calling.

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%, with defaults, min/max and descriptions already supplied for both page and limit. The description only adds the iteration hint to 'walk page with limit to see more of it', which is useful but does not add depth on limit bounds or page indexing. Baseline 3 applies.

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: browsing 'active national Bonus folder discounts, promotions ... and validity windows'. The word 'national' implicitly separates it from the personal-bonus siblings, but the description never names those siblings explicitly, so differentiation is inferential rather than stated.

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?

Usage is implied by 'Browse active ... discounts', and the pagination advice gives a practical cue for larger result sets. However, it gives no explicit when-to-use-this-vs-alternative guidance, e.g. versus ah_get_personal_bonus or ah_get_promo_digest, and no exclusions.

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

Deploy Server

Other Tools