Skip to main content
Glama

get_list

Reads a custom list's title, description, published and ranked flags, and its games in order.

Instructions

Read one custom list: title, description, published and ranked flags, and its games in order. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
list_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden; 'Read-only' explicitly declares the safety profile, which is genuine added value. It does not cover failure behaviour for an unknown list_id, permission/auth requirements, or whether 'its games in order' is capped or paginated — notable gaps for a no-annotation tool.

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?

Two short sentences, front-loaded with the resource and its returned fields, with the read-only note trailing. No filler, though the payload enumeration partly duplicates the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be described and the description is reasonable for a simple single-record read. Still missing is how a caller acquires a valid list_id and whether the embedded game list is truncated, which matters for correct invocation.

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 0%, so the only parameter, list_id, is undocumented in both schema and description. The phrase 'one custom list' implies an identifier is needed, but nothing explains its format or where to obtain it.

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 custom list') and enumerates the payload (title, description, published/ranked flags, ordered games), so the agent knows exactly what comes back. It stops short of naming how it differs from near-neighbours such as list_my_lists or list_collection, leaving the single-vs-many distinction to be inferred from 'one'.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus list_my_lists or other list/collection readers, and no prerequisites such as needing a list_id obtained from a listing call first. The only implicit cue is the word 'one', which signals single-record retrieval.

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