Skip to main content
Glama
Sign In
Ferret

Ferret

by ferret-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List items

list_items
Read-only

Browse inventory items, most recently changed first, with their storage locations; filter by location, container, category, tag, collection, origin, or wanted status.

Instructions

Lists items, most recently changed first, 50 at a time (offset for more), with where each is kept. Use it to browse rather than search: with locationId, everything in that place and the places inside it ("what's in the garage?"); containerItemId, what's directly in a box; categoryId, a category and its subcategories; tag, a tag's items (a tag can be a collection, e.g. "Christmas decorations"); origin, how they were added ("claude": what you added, to check your own work); collectionId (list_collections), a collection's things — wanted "include" adds its want list, "only" just that. To find a particular thing by name, use search_inventory.

Input Schema

NameRequiredDescriptionDefault
tagNoOnly items with this tag name (list_categories lists tags)
limitNoHow many items in this page
offsetNoHow many to skip, for the next page (total says how many there are)
originNoOnly things added this way: app, photos, walkthrough, roomscan, scan, label, spreadsheet, homeassistant, claude, api
wantedNoThe want list (things not owned yet): left out unless asked for
categoryIdNoOnly this category and its subcategories, from list_categories
locationIdNoOnly what's in this place and the places inside it, from list_locations
collectionIdNoOnly this collection's things, from list_collections
containerItemIdNoOnly what's directly inside this box (an item with isContainer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.1
    • addedInput schema / properties / categoryId / description
      Added value: +"Only this category and its subcategories, from list_categories"
    • addedInput schema / properties / collectionId / description
      Added value: +"Only this collection's things, from list_collections"
    • changedInput schema / properties / containerItemId / description
      Previous value: -"Only what's directly inside this box"New value: +"Only what's directly inside this box (an item with isContainer)"
    • addedInput schema / properties / limit / description
      Added value: +"How many items in this page"
    • addedInput schema / properties / locationId / description
      Added value: +"Only what's in this place and the places inside it, from list_locations"
    • addedInput schema / properties / offset / description
      Added value: +"How many to skip, for the next page (total says how many there are)"
    • addedInput schema / properties / tag / description
      Added value: +"Only items with this tag name (list_categories lists tags)"
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag readOnly/openWorld=false, but the description adds real behavior: default ordering, 50-per-page paging with offset, that the response carries each item's location, and that want-list items are excluded unless wanted='include'/'only'. That is context the annotations do not cover.

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-loaded with the core behavior before the filter catalog, and every clause carries information. It is dense and parenthetical-heavy, which makes it slightly harder to scan, but nothing is filler.

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

Completeness5/5

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

For a 9-parameter read tool with no output schema, it covers ordering, paging, the implicit total, response shape ('with where each is kept') and every filter's scope. An agent has enough to call it correctly on the first attempt.

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

Parameters5/5

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

Schema coverage is 100%, yet the description still adds meaning the schema lacks: locationId includes nested sub-places, containerItemId is direct contents only, categoryId includes subcategories, tag may act as a collection, and origin='claude' means things the agent itself added. These distinctions change how the filters are chosen.

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

Purpose5/5

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

States a specific verb ('Lists') and resource ('items'), plus the ordering ('most recently changed first'), page size and included location data. It explicitly separates itself from search_inventory, so an agent can pick it without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: 'Use it to browse rather than search' and 'To find a particular thing by name, use search_inventory.' Each filter is then framed by the question it answers ('what's in the garage?'), which is stronger than a bare when-to-use statement.

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

Deploy Server

Other Tools