Skip to main content
Glama

Just List

Read a list

get_list
Read-onlyIdempotent

Read one of the user's lists: its items with checked/unchecked state and the first names of the people it is shared with.

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's id (listId from list_my_lists, create_list or write_list_with_justy)

Output Schema

NameRequiredDescriptionDefault
urlNo
itemsNo
titleNo
statusYes
messageYes
openCountNo
sharedWithNoFirst names of the other people on the list
checkedCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds genuinely new behavioral context: it discloses that sharees are exposed only by first name, which is a privacy-relevant detail an annotation could never convey.

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?

One sentence, front-loaded with the action and resource, then the payload. Nothing is wasted and nothing relevant is buried.

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?

With an output schema present, the description needn't describe return shapes, and it still flags the notable parts (checked state, sharer first names). Annotations cover the safety profile and the only parameter is fully documented, so for a single-param read tool this is close to complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a single required parameter, and the schema already documents listId and its provenance. The description adds no format, range, or failure-mode meaning beyond that, which is the expected baseline when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read one of the user's lists') and enumerates what comes back: items with checked/unchecked state and sharer first names. It is clear enough to distinguish from write_list_with_justy or create_list, though it never names the sibling that lists all lists (list_my_lists), so differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'one of the user's lists' plus the schema note that listId comes from list_my_lists, create_list or write_list_with_justy hints at the workflow. There is no explicit when-to-use/when-not statement and no mention of alternatives for enumerating many lists.

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