Skip to main content
Glama
Sign In

LastList

by com.lastlistapp
OverviewDiscussionsAdmin

Mark items as already owned

have_items

Handle 'I already have X': take the item off the shopping list if it's there, and record it in the user's pantry/inventory if they aren't tracking it yet. Use for 'I already have rice', 'we've got plenty of olive oil', 'scratch the eggs, found some'. Use out_of_item for the opposite direction. Filler answers like 'all' or 'everything' are ignored rather than stored — if the user says something like that, ask which items they mean.

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

Input Schema

NameRequiredDescriptionDefault
itemsYesItem names the user already has, e.g. ['rice', 'olive oil'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses the real side effects: removal from the list plus a conditional inventory write, and the policy that filler values like 'all'/'everything' are ignored rather than stored. It does not cover duplicate handling, partial failure between the two writes, or what is reported back.

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?

Front-loaded with the core effect, then usage triggers, then the sibling contrast, then the edge case. Every sentence carries distinct information and the conversational examples are functional, not filler.

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

Completeness5/5

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

Single required array parameter, full schema coverage, annotations present, no output schema expected. The description covers effect, triggers, alternative, and the main input pitfall — nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds real value by warning that certain values ('all', 'everything') are silently discarded and must be clarified with the user rather than passed through, which the schema does not state.

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 specific effects on two resources: removes items from the shopping list and records them in pantry/inventory. The title-plus-description pairing makes the operation unambiguous, and 'Use out_of_item for the opposite direction' anchors it against a sibling.

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?

Explicit when-to-use with three natural-language triggers ('I already have rice', 'we've got plenty of olive oil', 'scratch the eggs'), an explicit alternative for the inverse case (out_of_item), and a fallback instruction for filler answers.

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

All LastList 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