Skip to main content
Glama

BotShelf Vampire

List items

list_items
Read-onlyIdempotent

List items in shelf order, with optional filters, a page at a time. Also returns how many items each kind holds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoKind of item, for example team, build, toolkit, grokbot, trade, guide, field. list_items returns the kinds that exist.
limitNoHow many items (default 10).
topicNoTopic label exactly as shown on the shelf, for example "Research".
accessNoopen = full text readable without sign-up. paid = listed, text not available here.
offsetNoPosition to start from (default 0).
checkedNotrue = only items with a recorded check.
runs_onNoWhere it runs, exactly as shown on the shelf, for example "Claude Code", "Grok Bot", "Ollama", "TradingView".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: results come back paginated and the response includes per-kind counts, which is return-value context that matters because there is no output schema. It omits whether a total count or 'has more' indicator is returned, which an agent paging through results would want.

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 with no filler, and the core operation plus ordering and pagination are front-loaded. The trailing clause about kind counts is useful but sits apart from the rest and could have been tied more tightly to the paging behavior.

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?

For a zero-required-parameter listing tool with 7 well-documented params and no output schema, the description covers the essentials but leaves the response shape underspecified: it mentions kind counts but not how paging terminates or what an item record contains. An agent can call it correctly but may need a trial call to understand the return payload.

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% and every parameter carries a description with examples and enum values, so the schema does the heavy lifting. The description adds only the general notion of 'optional filters' and confirms the kind vocabulary exists on the shelf; it adds no semantics for limit, offset, topic, access, checked or runs_on beyond the schema.

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 ('List items') plus the ordering ('shelf order') and pagination ('a page at a time'), which is enough to tell a browse operation apart from a search operation. It never names search_items or get_item, so the differentiation is implied by 'shelf order' 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?

The phrase 'with optional filters' and 'a page at a time' implies this is the enumeration/paging tool, contrasting implicitly with the search and single-fetch siblings. There is no explicit when-to-use or when-not-to-use statement, and no guidance on switching to search_items when the agent has a query rather than a shelf browse.

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.