Skip to main content
Glama
olgasafonova

TilbudsTrolden

by olgasafonova

score_recipes

Score saved recipes against current deals to find the cheapest meals, optionally optimizing a weekly plan and showing deal coverage and cost.

Instructions

Score all saved recipes against current deals, optionally optimize a weekly meal plan. USE WHEN: deciding what to cook based on current deals ('what's cheapest this week'), comparing recipe costs. NOT FOR: generating a shopping list (use generate_shopping_list or plan_and_shop). Shows deal coverage %, estimated cost, and confidence levels per ingredient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoDays to plan (default 7)
optimizeNoAlso generate optimal weekly plan
maxSlowDaysNoMax slow-cook days in plan (default 2)
maxPerCuisineNoMax same cuisine in plan (default 2)
maxPerProteinNoMax same protein in plan (default 2)
preferCuisinesNoSoft cuisine preferences: {"asian": 3} = prefer at least 3 Asian dishes. Best-effort, won't fail if impossible.
slowOnlyOnDaysNoRestrict slow recipes to these days only (1-indexed). E.g. [6, 7] for weekends
excludeProteinsNoDietary exclusions. Checks both recipe type and individual ingredients. E.g. ["pork"] also catches bacon in vegetarian recipes. Options: pork, beef, lamb, fish, shellfish, dairy, gluten, beans, nuts, egg
allowProteinOnDaysNoPer-day exceptions for excluded proteins (1-indexed). E.g. {"pork": [2]} = allow pork on day 2 (Tuesday)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.5.1

TDQS

A4.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not explicitly state whether the tool is read-only or if 'optimize' modifies data. The description reveals output details but lacks side-effect warnings.

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 sentences with essential information: purpose, usage guidance, and output summary. No wasteful words, front-loaded with the verb and resource.

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?

While usage and guidelines are clear, the description lacks a comprehensive explanation of the return value. With no output schema, it only vaguely mentions 'deal coverage %, estimated cost, and confidence levels' without specifying structure or format.

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

Parameters5/5

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

With 100% schema coverage, the description adds significant value beyond the schema by explaining behavior (e.g., 'excludeProteins checks both recipe type and individual ingredients', 'preferCuisines is best-effort'). This compensates for complex parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('score') and resource ('saved recipes against current deals') and distinguishes from siblings by explicitly stating what it is not for (generating shopping list) and naming alternatives (generate_shopping_list, plan_and_shop).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit USE WHEN context ('deciding what to cook based on current deals') and NOT FOR conditions with alternative tools, giving clear guidance on when to invoke this tool versus siblings.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/olgasafonova/tilbudstrolden-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server