LastList

Create a list

create_list

Create a new list for the user (e.g. 'make a Costco list', 'start a party list', 'set up a baby registry'). Defaults to a shopping list. The list appears in the user's LastList app and is labeled as created by you. Ask the user before creating a list they didn't request.

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": {
      "title": "<title>"
    },
    "name": "create_list"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Name of the list, e.g. 'Costco'.
`listType`	No	List type. Defaults to 'shopping'.
`registryOccasion`	No	For wishlists only: what the registry is for. Set it when the user names an occasion ('wedding registry', 'baby shower list'), which lets the app title the registry and its printed insert properly. Leave it off for a plain wishlist.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

While annotations specify that the tool is write-capable (readOnlyHint: false), the description adds rich behavioral context by noting the list appears in the 'LastList app' and is 'labeled as created by you,' which informs the agent about the resulting data state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is succinct and highly functional. It front-loads the definition, provides concrete examples, and concludes with an essential procedural guardrail.

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?

Given the comprehensive 100% schema coverage, the description is complete. It clarifies the output visibility (appears in the app) and the necessary interaction model (ask permission before creating).

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?

Although schema coverage is 100%, the description adds significant semantic value by explaining how `listType` and `registryOccasion` are conceptualized through user input examples like 'Costco list' or 'baby registry.' It helps the agent map natural language requests to the specific enums.

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 purpose is clearly defined as creating a new list. It provides strong, specific examples of use ('Costco list', 'baby registry') which immediately informs the AI of the tool's practical application.

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 description provides critical operational guidelines by stating that the default type is 'shopping' and, crucially, it sets a guardrail: 'Ask the user before creating a list they didn't request.' This tells the agent exactly when to trigger the tool and when to wait.

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

All LastList tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?