Skip to main content
Glama

Add a shared list item

zarok_add_shared_list_item

Adds one item to a shared list. Other members of the list see the new item as added by the user. Not covered by the 24-hour plan undo: the user can remove it in Zarok. Requires an editor or owner role. A repeated request_id adds the item once. Optional assignee: "me", a member name as the user said it, or an @username; if it does not match exactly one member who can edit, nothing is added and the tool asks to clarify with the user.

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": {
      "request_id": "<request_id>",
      "list_id": "<list_id>",
      "title": "<title>"
    },
    "name": "zarok_add_shared_list_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoA calendar date in the user’s local time, YYYY-MM-DD
noteNo
titleYes
list_idYesA shared list id from zarok_get_shared_lists
assigneeNoWho should do it: "me", a list member name as the user said it, or an @username
priorityNo
request_idYesA new unique id for this request; reuse it only to retry the identical request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / assignee
      Added value: +{
      +  "description": "Who should do it: \"me\", a list member name as the user said it, or an @username",
      +  "maxLength": 40,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"A calendar date in the user’s local time, YYYY-MM-DD"
    • addedInput schema / properties / list_id / description
      Added value: +"A shared list id from zarok_get_shared_lists"
    • addedInput schema / properties / request_id / description
      Added value: +"A new unique id for this request; reuse it only to retry the identical request"
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false) it discloses the multi-user visibility effect, the absence of plan-level undo, the role gate, retry de-duplication via request_id, and the exact failure path when an assignee is ambiguous ('nothing is added and the tool asks to clarify'). The request_id de-dupe statement refines rather than contradicts idempotentHint=false, since each distinct request_id is still a fresh write.

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 action and effect, then prerequisites, idempotency and the assignee rule – every sentence carries operational information. The final sentence restates the assignee forms already in the schema before adding the matching-failure behavior, a small redundancy that keeps it from a 5.

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 7-parameter mutation with no output schema, the definition covers role requirements, side effects, retry semantics, and the ambiguous-assignee outcome. It does not say what a successful call returns (e.g. an item id) or confirm what happens to unspecified fields, minor gaps for an add operation.

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?

With schema coverage at 57% across 7 parameters, the description adds real meaning for the two riskiest ones: request_id ('reuse it only to retry the identical request') and assignee (accepted forms plus the exactly-one-editable-member matching rule and what happens on failure). title, note, date and priority are left to the schema, but those are largely self-describing.

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?

The first sentence states a specific verb and resource ('Adds one item to a shared list') and immediately adds the social scope (other members see the new item as added by the user), which separates it from sibling readers like zarok_get_shared_lists and from zarok_set_shared_list_item_done.

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 clear preconditions ('Requires an editor or owner role') and the consequence of acting ('Not covered by the 24-hour plan undo: the user can remove it in Zarok'), which tells an agent when the call is appropriate and what follow-up to expect. It never names an alternative tool or an explicit when-not-to-use case, so it stops short of a 5.

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