Skip to main content
Glama

List items

list_items
Read-only

Items in a project: named things a piece of work keeps coming back to, of kind character, place, object, style, sequence or set. Each has id, slug, name, kind and starred_take_id. Filter by kind. project is its id or slug. Items are addressed by id, slug or @slug (the form used in prompts) wherever a tool takes item.

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": {
      "project": "<project>"
    },
    "name": "list_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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 readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds valuable domain context (what an item is, what fields it exposes, how it is addressed in prompts), but says nothing about ordering, pagination, result limits, or what an empty project returns. Useful context, but not rich behavioral disclosure beyond the annotations.

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-loads the resource and its definition, then moves to fields, filtering, and addressing in a logical order with no duplicated sentences. The opening gloss ('named things a piece of work keeps coming back to') is evocative but slightly loose for a machine-facing definition; otherwise every sentence carries information.

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, return values need not be described, and the description instead supplies the domain model an agent needs to interpret results and the addressing convention used across tools. Parameter and filtering behavior are covered. The only gap is operational detail such as ordering or pagination, which matters little for a read-only list call.

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 0%, so the description carries the full burden and largely meets it: it names both parameters, explains that `project` accepts an id or slug, and enumerates the valid `kind` values (character, place, object, style, sequence or set) even though the schema has no enum. It stops short of a 5 by not specifying matching semantics for `kind` or whether it is case-sensitive.

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 the resource (items in a project) and defines the domain concept concretely, including the six kinds and the fields each item carries. It also explains how items are addressed (id, slug, `@slug`), which separates it from retrieval-style siblings. It never states 'list' as the verb outright and does not explicitly contrast with get_item or list_takes, so it falls short of a 5.

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?

'Filter by `kind`' and '`project` is its id or slug' imply the primary usage pattern, but there is no explicit guidance on when to call this versus get_item (for one known item) or other list_* tools. No exclusions or preconditions are given; usage is inferable rather than stated.

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