Skip to main content
Glama
Sign In
PoB PoE2 MCP

PoB PoE2 MCP

by Hecatoncheir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pob_trade_search

Read-only

Builds a Path of Exile 2 trade2 browser link from Path of Building slot, league, base, budget, and stat filters. Use it to find upgrades without sending network requests or altering your build.

Instructions

Подготовить браузерную ссылку trade2 по каталогу PoB: лига, ячейка, база, бюджет и характеристики. Сетевые запросы не выполняются; рабочая сборка не изменяется.

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": {
      "slot": "<slot>",
      "league": "<league>"
    },
    "name": "pob_trade_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNo
slotYes
leagueYes
onlineNo
filtersNo
currencyNo
maxPriceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.0

TDQS

B3.3/5.0
Behavior3/5

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

The two clauses 'no network requests are performed' and 'the working build is not modified' are genuinely useful for a tool whose name suggests live trading, but they largely restate the supplied annotations (openWorldHint=false, destructiveHint=false, readOnlyHint=true). No additional behavior, such as link expiry, URL length limits, or failure modes, is disclosed.

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?

Two short sentences with no waste: the artifact and its inputs come first, followed by the non-side-effect guarantees. Nothing needs to be cut.

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?

The return value (a browser link) is implied clearly, which compensates for the missing output schema, and the required slot/league fields are named. Still, for a 7-parameter tool with zero schema documentation, the absence of parameter formats and the omission of 'online' leave real gaps.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it does map several fields by name: league, slot ('ячейка'), base, budget and characteristics. However, it omits 'online', does not distinguish currency from maxPrice under 'budget', and gives no format guidance for filter ids or slot identifiers.

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?

The description states a concrete verb and artifact: build a browser trade2 link from the PoB catalog, covering league, slot, base, budget and characteristics. This lets an agent distinguish it from sibling pob_trade_catalog, which presumably queries the catalog, though the sibling is not named explicitly.

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 explicit when-to-use guidance, no prerequisite statement, and no named alternative such as pob_trade_catalog or pob_inspect_item. The only usage-relevant signal is the implicit hint that this prepares (rather than performs) a search, which an agent must infer.

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