POE2MarketMCP

Overview Schema Source Related Servers Score Discussions Admin

list_stash_items

List all items in your Path of Exile 2 stash with quantities, including unpriced items. Group stacks across tabs or filter by search, tab, rarity to see your real inventory.

Instructions

List what is actually in your stash: every item, with quantities.

Reads the most recent snapshot. Set group_stacks (the default) to aggregate the same item across tabs — 3 stacks of Exalted Orbs in three tabs become one row with the combined quantity, which is almost always the question being asked. Turn it off to see each physical stack and its tab.

Unpriced items (gear, maps, anything without a collected price) are included with a null value rather than dropped, so the list is a real inventory rather than only the part we happen to have priced.

Filters: search matches name or base type, tab matches a tab name, rarity is Normal/Magic/Rare/Unique/Currency/Gem.

Input Schema

TableJSON Schema

Name	Required	Default
`tab`	No
`sort`	No	value
`limit`	No
`league`	No
`offset`	No
`rarity`	No
`search`	No
`priced_only`	No
`group_stacks`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description carries the full burden, and it delivers: snapshot-based reads, stack-grouping behavior, null values for unpriced items, and filter semantics. It is transparent about behaviors an agent would otherwise have to infer or test.

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

Conciseness5/5

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

Four short thematic paragraphs with front-loaded purpose, a concrete example, and a compact filter list. There is no filler and no repetition of schema defaults.

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?

The output schema covers return shape, and the description covers behavior and filter usage, so an agent can invoke it correctly with no arguments or with a meaningful filter. Minor gaps such as league default, priced_only semantics, and pagination behavior keep this from a 5.

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?

The description adds real meaning for group_stacks with a concrete example, plus semantics for search, tab, and rarity. However, with 0% schema coverage and 9 parameters, it leaves sort, limit, offset, league, and priced_only to be inferred from names and defaults.

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?

The opening states a specific verb and resource: 'List what is actually in your stash: every item, with quantities.' This clearly distinguishes it from priced-only, history, or search-oriented sibling tools.

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?

The description gives clear usage context: it reads the latest snapshot, aggregates stacks by default, and includes unpriced items so the result is a real inventory. It does not explicitly name alternatives such as search_items or get_stash_value, so it stops short of full when/not guidance.

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

Install Server