Skip to main content
Glama

Get one saved list

get_list
Read-onlyIdempotent

One named list: alreadyOnThis, pendingReview, source, and share roster. Does not use credits. An alert companion is the same match set as that alert (every match except dismissed; pending review stays in). A filter or polygon list with no saved records is a saved search. get_list_results reads the planned projects on this list, and get_list_permits reads its building permits.

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 public id ("lst_…"), from list_user_lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond them with 'Does not use credits' and with domain semantics of what membership means for alert companions and saved searches. It says nothing about permissions/access scope for shared lists or about ordering and size of the returned set.

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

Conciseness3/5

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

Every sentence carries content – credit cost, alert semantics, saved-search edge case, sibling routing – but the opening is a fragment that lists output fields before saying what the call does, and terms like 'source' and 'share roster' are left unglossed. It is dense and front-loading could be improved by leading with the action.

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 one-parameter read tool with full annotation coverage and no output schema, the description does the job that matters: it characterizes the returned membership sets and clarifies ambiguous concepts. Remaining gaps (access requirements, list ordering) are minor for a read-only getter.

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 description coverage is 100% and the single parameter is documented in the schema, including the 'lst_…' format and its provenance from list_user_lists, so the baseline is 3. The description adds no meaning about listId beyond stating the resource is a 'named list.'

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?

The description identifies the resource (a single saved list) and enumerates what it returns – alreadyOnThis, pendingReview, source, share roster – plus explicit disambiguation of the concept (an empty filter/polygon list is really a saved search). It stops short of a clean verb-first statement of the action, opening with a telegraphic fragment rather than 'Retrieve one saved list by id,' but an agent still knows what it gets back.

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

Usage Guidelines4/5

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

It routes the agent to siblings by task: get_list_results for planned projects and get_list_permits for building permits, and explains the alert-companion case so the agent knows this tool still applies. It does not state when to prefer this over list_user_lists (enumeration) or add_permits_to_list (mutation), so the exclusions are implicit rather than explicit.

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