Skip to main content
Glama
Sign In

hunchful

by io.hunchful
OverviewDiscussionsAdmin

Household: tick items off the shopping list

check_shopping_items
Idempotent

Tick things off a list (bought), or untick them with done: false: itemIds from household_info (part list). Only when the person says they bought them. Their own list (to: me): done at once. The household's: a card they tap in Hem.

Input Schema

NameRequiredDescriptionDefault
toNome = their own list; default the household's.
doneNotrue = bought (default), false = back on the list.
itemIdsYesitemIds from household_info, e.g. ["3fa9c1b2d4e6"].
householdNoThe household's name or householdId from list_households, e.g. "Hemma". Leave out when the person has only one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / itemIds / description
      Previous value: -"itemIds from read_shopping_list, e.g. [\"3fa9c1b2d4e6\"]."New value: +"itemIds from household_info, e.g. [\"3fa9c1b2d4e6\"]."
    • addedInput schema / properties / to
      Added value: +{
+  "description": "me = their own list; default the household's.",
+  "enum": [
+    "me",
+    "home"
+  ],
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "changed": {
-      "type": "number"
-    },
-    "done": {
-      "type": "boolean"
-    },
-    "household": {
-      "additionalProperties": false,
-      "properties": {
-        "householdId": {
-          "type": "string"
-        },
-        "name": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "householdId",
-        "name"
-      ],
-      "type": "object"
-    },
-    "itemId": {
-      "description": "The Stream card, when it's a draft.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "itemIds": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "items": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "note": {
-      "type": "string"
-    },
-    "status": {
-      "enum": [
-        "done",
-        "draft"
-      ],
-      "type": "string"
-    },
-    "why": {
-      "description": "Why it's a draft (said to the person).",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "status",
-    "household",
-    "itemIds",
-    "items",
-    "done",
-    "note"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the person's own list is 'done at once' whereas the household's list involves 'a card they tap in Hem.' However, it is unclear whether the household case actually completes the tick or defers it to a UI card, which is exactly the ambiguity an agent needs resolved for a mutation tool.

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

Conciseness3/5

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

It is short and front-loads the action, but the telegram-style colons ('or untick them with done: false: itemIds from household_info (part list)') and the fragment 'The household's: a card they tap in Hem' make it harder to parse than it needs to be. Brevity here costs clarity rather than earning it.

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?

With full schema coverage and no output schema, the description only needs to carry behavior, and it does cover the two list targets and the untick path. It leaves the household-case outcome and the required 'household' disambiguation partially unexplained, which for a mutation tool is a meaningful gap.

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 description coverage is 100%, so the schema already documents 'to' (me vs household, default), 'done' (true=bought, false=back on list) and itemIds with an example. The description restates the same semantics ('untick them with done: false', 'their own list (to: me)') without adding format or edge-case guidance, so it does not exceed the baseline.

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 states a specific verb and resource: tick items off (bought) or untick them (done: false) on a shopping list. It names the source of the identifiers (household_info part list) and distinguishes the person's own list from the household list, so an agent can tell it apart from add_to_list. The phrasing is terse and the 'card they tap in Hem' clause blurs the purpose slightly.

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 gives an explicit trigger condition: 'Only when the person says they bought them,' which functions as both a when-to-use and a when-not-to-use rule. It also tells the agent where the itemIds come from (household_info), which is the necessary prerequisite. It never explicitly contrasts with the sibling add_to_list, so the alternative is only implied.

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

All hunchful toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources