Skip to main content
Glama
MaxWilk

poe2-build-mcp

by MaxWilk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_unique

Retrieve the full readable text of a unique item, including base and mods, by providing its name. If the name is a base type, it redirects to the appropriate tool.

Instructions

Return a unique item's full readable text (base, mods) by name.

If the name is a base type rather than a unique (e.g. "Warmonger Bow"), says so and points to get_item, instead of returning a confusing null.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.23
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "anyOf": [
-      {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Result"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"get_uniqueOutput"New value: +"get_uniqueDictOutput"
  2. First observedv0.1.6

TDQS

A4.7/5.0
Behavior4/5

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

Discloses the exceptional behavior for base types, but does not mention any other traits like read-only or side effects. With no annotations, this is adequate for a simple read tool.

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 sentences front-loaded with the main purpose, no superfluous words.

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?

Covers all relevant aspects for a single-parameter tool with an output schema: core behavior and edge case.

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?

The description explains the 'name' parameter is the unique item name and clarifies edge-case handling. Given 0% schema coverage, it adds necessary meaning.

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 description clearly states the tool returns a unique item's full readable text by name, and distinguishes from get_item by handling base type names.

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?

Explicitly says to use when you have a unique item name, and for base types it directs to get_item instead of returning null.

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