Skip to main content
Glama

add_items

Lägg till en eller flera varor (fri text, t.ex. 'mjölk', '2 kg potatis') på en inköpslista. Utelämna list_name för den primära listan.

Instructions

Lägg till en eller flera varor (fri text, t.ex. 'mjölk', '2 kg potatis') på en inköpslista. Utelämna list_name för den primära listan.

Kategori är valfri och anges med namnen från ICA-appen (t.ex. 'Mejeri', 'Frukt & Grönt', 'Städ & disk', 'Djur'). Utelämnad väljer ICA kategori utifrån varans namn, vilket räcker för vanliga matvaror. category gäller alla varor i anropet; en vara kan också ges som {"name": ..., "category": ...} med egen kategori, så att en blandad korg går i ett anrop.

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": {
      "items": "<items>"
    },
    "name": "add_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
categoryNo
list_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • addedInput schema / $defs
      Added value: +{
      +  "Item": {
      +    "description": "En vara med egen kategori.",
      +    "properties": {
      +      "category": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Category"
      +      },
      +      "name": {
      +        "title": "Name",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "title": "Item",
      +    "type": "object"
      +  }
      +}
    • addedInput schema / properties / category
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Category"
      +}
    • addedInput schema / properties / items / items / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "$ref": "#/$defs/Item"
      +  }
      +]
    • removedInput schema / properties / items / items / type
      Removed value: -"string"
  2. First observedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the omit-list_name default, the auto-categorization fallback, and the scoping rule that top-level category applies to all items while per-item categories override. It leaves out duplicate handling, permission requirements, and what happens if the named list does not exist.

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-loaded with the core action and default behavior, then the category rules. The examples earn their space, though the category paragraph is dense and could be tightened slightly.

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 3-parameter tool with an output schema and no annotations, the description covers everything needed to invoke it correctly, including the polymorphism of items. The only gap is guidance on whether to prefer this over add_product_to_shopping_list for known products.

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?

Schema description coverage is 0%, yet all three parameters are explained in prose: items as free text with concrete examples ("mjölk", "2 kg potatis"), category with the expected ICA vocabulary ("Mejeri", "Frukt & Grönt"), and list_name defaulting to the primary list. It also documents the polymorphic item form {"name": ..., "category": ...}, which the schema alone would not convey.

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?

States a specific verb and resource ("Lägg till ... varor ... på en inköpslista") and pins down scope with "fri text", which implicitly separates it from product-based siblings like add_product_to_shopping_list. An agent can tell what this does without opening the schema.

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?

Explains the key selection decision for the default list ("Utelämna list_name för den primära listan") and when category can be omitted (ICA auto-categorizes common groceries). It never explicitly contrasts itself with add_product_to_shopping_list, so the agent must infer that free-text items belong here.

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