Skip to main content
Glama

Shared lists

zarok_get_shared_lists
Read-onlyIdempotent

Returns the user’s shared lists (to-do lists shared with family or friends in the Zarok app) with the user’s role and counts, or, with list_id, the items of one list: title, note, date, priority, done and whether the item is assigned to the user. Names of other members, comments, files, invitations and secret tasks are not included. Item texts are written by list members. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zarok_get_shared_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idNoA shared list id from zarok_get_shared_lists

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / list_id / description
      Added value: +"A shared list id from zarok_get_shared_lists"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new context, namely the content boundaries (no member names, comments, files, invitations, secret tasks) and the note that item texts are member-authored, which flags untrusted input. It does not describe pagination or volume limits on list counts, which is the only missing behavioral detail.

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?

A single dense paragraph that front-loads the primary behavior and then the conditional mode. Every clause carries information an agent needs, though the two modes packed into one sentence make it slightly harder to parse than separate sentences would.

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?

With no output schema present, the description compensates by enumerating return fields for both modes and scoping out excluded data. For a single-optional-parameter read tool, nothing an agent needs in order to call it or interpret the result 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% and the sole parameter is documented in-schema, so the baseline is 3. The description goes beyond that by explaining the semantic effect of supplying list_id (switches the response from list summaries to per-item records with a specific field set), which the schema text alone does not convey.

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 ('returns the user's shared lists') and distinguishes its two modes: list summaries with role and counts, versus the items of one list when list_id is supplied. It even enumerates the returned item fields, so an agent knows exactly what this call surfaces.

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?

The conditional 'or, with list_id, the items of one list' tells the agent precisely which call shape to pick for which need, and the exclusion sentence ('names of other members, comments, files, invitations and secret tasks are not included') prevents the agent from reaching for this tool expecting that data. The mutation siblings (add item, set done) are implicitly ruled out by the read-only framing.

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