Skip to main content
Glama

Just List

Draft a list with Justy

draft_list
Read-only

Turn one sentence about a plan or errand (for example "Friday dinner for 8", "packing for a weekend with kids", "ערב שישי ל-8") into a ready-to-use list written by Justy. No account needed. Returns the items (grouped by aisle for shopping lists) and a justlistapp.com link where the user can keep the list, share it, or open it in the app. Use this when the user wants a list drafted and has not connected a Just List account; with a connected account prefer write_list_with_justy, which saves it.

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": {
      "sentence": "<sentence>"
    },
    "name": "draft_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for the list when the sentence alone is ambiguous: he (Hebrew) or en (English). Defaults to the sentence's language.
sentenceYesThe user's request in one sentence, in their own words and language

Output Schema

NameRequiredDescriptionDefault
kindNo
titleNo
statusYes
keepUrlNoOpens the draft on justlistapp.com, where the user can save it to their account or get the app
messageYes
languageNo
sectionsNo
itemCountNo
alternativeUrlNoWhere to make the list without Justy

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, destructiveHint=false, openWorldHint=false, so the safety profile is covered; the description adds genuinely new context: no account is required and the result includes a hosted share/keep link. It does not explain the implications of idempotentHint=false (repeated calls yield distinct drafts/links), which is the one behavioral gap.

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 transformation, then output, then routing guidance — a logical order with no filler. The first sentence carries several parenthetical examples that make it longer than strictly necessary, but each sentence contributes distinct information.

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?

For a two-parameter, read-only drafting tool with an output schema and full annotations, nothing an agent needs is missing: purpose, input shape, no-auth requirement, return content, and the sibling to use instead when an account is connected are all stated.

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 both parameters are already documented. The description still adds value by showing what a valid 'sentence' looks like ('Friday dinner for 8', 'packing for a weekend with kids') and by giving a Hebrew example that demonstrates the language auto-detection the 'lang' parameter falls back on.

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 description gives a specific verb ('Turn...into a ready-to-use list'), names the resource (a list, grouped by aisle for shopping), and states what the output is (items plus a justlistapp.com link). It explicitly contrasts itself with write_list_with_justy, so an agent can separate the two without opening either schema.

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?

States the trigger ('when the user wants a list drafted'), the required precondition ('has not connected a Just List account'), and the alternative with its distinguishing behavior ('with a connected account prefer write_list_with_justy, which saves it'). This is an explicit when/when-not/alternative routing rule.

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