Skip to main content
Glama

Add an errand to my list

add_errand

Adds one errand to the connected person's own list, in their words ('milk and eggs', 'pick up lotion at the pharmacy'), the way the app, Siri and a text to Scout do: Scout reads the store kind from the words and fits the errand into a drive they already make. Optional 'by': a day word (today, tomorrow, Friday) or a date (YYYY-MM-DD). Returns the item as the list shows it, a confirmation line, and whether a stop on one of today's drives already fits; a stop is named only when Scout matched one, never guessed. Call this only when the person asks to add something. Needs a connected account.

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": {
      "text": "<text>"
    },
    "name": "add_errand"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoA day word (today, tomorrow, Friday, next Monday) or an ISO date. Omit when they named no day.
textYesWhat they need, in their words. A store named after 'at' or 'from' is kept and honoured.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the write/duplicate profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the safety bar is lower. The description adds real value on top: it discloses account requirements, that store kind is inferred by Scout, that a drive match happens automatically, and that a stop is 'named only when Scout matched one, never guessed'.

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 mostly free of filler, though the 'the way the app, Siri and a text to Scout do' clause and the return-value sentence add length. The three-part return explanation is arguably redundant given an output schema exists.

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?

Covers purpose, gating, prerequisites, parameter intent and behavior for a low-complexity two-parameter tool, and it restates return values even though an output schema exists. Nothing an agent needs to invoke 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 goes slightly beyond the schema by clarifying that 'by' accepts a day word or YYYY-MM-DD and should be omitted when no day is given, and by explaining that text is interpreted in the user's own words with store names after 'at'/'from' preserved.

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 ('Adds one errand to the connected person's own list') and explains the natural-language capture model ('milk and eggs', 'pick up lotion at the pharmacy'). This cleanly separates it from siblings like my_list (viewing) and circle_needs (shared/observed needs), so an agent can disambiguate without opening schemas.

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?

Gives an explicit gating condition – 'Call this only when the person asks to add something' – plus the prerequisite 'Needs a connected account'. It does not name a specific sibling alternative (e.g. save_spot vs. my_list) for the adjacent cases, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources