Skip to main content
Glama
Sign In

LastList

by com.lastlistapp
OverviewDiscussionsAdmin

Get a list

get_list
Read-only

Reads one list in full: its title, type, and every item on it with quantities and whether each has been checked off. This is what answers 'what's on my list', what shows whether an item is already present, and what reads the pantry's contents.

It takes a list id, which is one of the ids returned by search_lists. search_lists returns the lists themselves; this returns the contents of one of them.

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": {
      "listId": "<listId>"
    },
    "name": "get_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe list id, exactly as returned by search_lists. Not the list's title; ids are opaque strings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / listId / description
      Previous value: -"The list id returned by search_lists"New value: +"The list id, exactly as returned by search_lists. Not the list's title; ids are opaque strings."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, dropping the safety burden, and the description adds real behavioral detail: the read is complete ("every item"), covers checked state and quantities, and is scoped to a single list. It does not say what happens when the id is unknown or malformed, which is the remaining 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 outcome, then a short routing note. The second paragraph lightly repeats the schema's own wording about ids coming from search_lists, which is the only redundancy in an otherwise tight definition.

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 single-parameter read with no output schema, the description supplies an adequate picture of the return payload and the input's origin. Only error/empty-list behavior is unstated, which is minor at this complexity.

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 the baseline is 3, but the description adds provenance the schema only hints at — the id must come from search_lists and is opaque rather than a title. That directly prevents a plausible misuse (passing a list name).

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 ("Reads one list in full") and enumerates exactly what is returned: title, type, every item, quantities, checked state. It explicitly differentiates itself from search_lists, so an agent can choose between them without opening the 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?

Names the concrete questions this answers ("what's on my list", whether an item is already present, reading the pantry's contents) and states the routing rule against the sibling: "search_lists returns the lists themselves; this returns the contents of one of them." No inference is required.

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

All LastList toolsInspect
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