Errand Runs MCP Server

log_item

Records an errand item and tags it with stores that can sell it; items without a store tag remain unplanned until tagged.

Instructions

Log one errand item and tag it with the store(s) that can sell it (for example ["Canal Market", "Maple Drugstore"]). Quantity defaults to 1. Leaving stores empty still logs the item, but it cannot be planned into a run until it has a store tag.

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": {
      "item": "<item>"
    },
    "name": "log_item"
  }
}

Input Schema

Name	Required	Description	Default
`item`	Yes
`note`	No
`stores`	No
`quantity`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden; it usefully discloses the default quantity and the downstream consequence of an empty stores list. It is silent on whether logging an existing item creates a duplicate, what permissions are needed, and whether the action is reversible — meaningful gaps for a write operation.

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?

Three short sentences, front-loaded with the action, and the parenthetical example for stores earns its space by showing the expected value shape. Little wasted wording, though the clause about planning could be tightened.

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?

With four parameters, an output schema present, and no annotations, the description covers the essential call mechanics and the one non-obvious constraint. The residual gap is duplicate/identity behavior on re-logging and the meaning of 'note', which an agent would need in ambiguous cases.

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 0%, so the description must compensate. It explains stores with a concrete example format and documents the quantity default, but leaves 'note' completely undefined and never describes 'item' beyond the title, so one of four parameters is uninterpretable from any source.

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?

States a specific verb and resource ('Log one errand item') plus the tagging behavior, which is enough to tell it apart from list_items, mark_bought, or tally. It stops short of explicitly naming a sibling, but the reference to items being 'planned into a run' implicitly contrasts with plan_run.

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

Usage Guidelines3/5

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

Gives one concrete conditional: leaving stores empty is allowed but blocks planning into a run, which is real usage guidance. It does not say when to use this versus mark_bought or receipt, nor whether re-logging an existing item duplicates it, so guidance is partial rather than explicit.

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

Deploy Server