Skip to main content
Glama
crithitstudio

hypixel-skyblock-mcp

by crithitstudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Look Up SkyBlock Item

skyblock_item
Read-onlyIdempotent

Look up a Hypixel SkyBlock item by ID or name to get official metadata, Bazaar prices, or lowest-BIN value, with optional wiki context and candidate IDs for ambiguous searches.

Instructions

Look up a single SkyBlock item by ID or name and return its official metadata (tier, category, stats, NPC price, museum/soulbound flags) plus a live value: full Bazaar buy/sell/spread/volume for Bazaar items, or a lowest-BIN price when an external source is configured, otherwise a clear auction-only note. Set includeWiki for configured MediaWiki obtaining/usage/upgrading/history context. Ambiguous searches return candidate IDs instead of guessing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdNoExact SkyBlock item ID, for example HYPERION or ENCHANTED_DIAMOND.
searchNoItem name or substring when the exact ID is unknown.
priceBasisNoPrice basis used only for the lowest-BIN fallback.buy
includeWikiNoFetch configured wiki context (or official-wiki retirement information) for the resolved item.
maxCandidatesNoMax candidate IDs to return for an ambiguous search.
includeBazaarOrdersNoInclude top Bazaar buy/sell order summaries for Bazaar items.
maxWikiSectionCharsNoMaximum characters per wiki section when includeWiki is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.0
    • changedInput schema / properties / includeWiki / description
      Previous value: -"Fetch official Hypixel SkyBlock Wiki context for the resolved item."New value: +"Fetch configured wiki context (or official-wiki retirement information) for the resolved item."
    • addedInput schema / properties / itemId / maxLength
      Added value: +256
    • addedInput schema / properties / search / maxLength
      Added value: +256
  2. Changed2 schema fields changedv1.0.4
    • addedInput schema / properties / includeWiki
      Added value: +{
+  "default": false,
+  "description": "Fetch official Hypixel SkyBlock Wiki context for the resolved item.",
+  "type": "boolean"
+}
    • addedInput schema / properties / maxWikiSectionChars
      Added value: +{
+  "default": 900,
+  "description": "Maximum characters per wiki section when includeWiki is true.",
+  "maximum": 2500,
+  "minimum": 200,
+  "type": "integer"
+}
  3. First observedv1.0.1

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint/idempotentHint/openWorldHint already covering the safety profile, the description adds meaningful non-annotation behavior: ambiguous searches degrade to a candidate list instead of guessing, the lowest-BIN price is contingent on an external source being configured (otherwise a plain auction-only note), and wiki retrieval can include official-wiki retirement information. These conditionals are exactly the kind of runtime conduct annotations cannot express.

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?

Three front-loaded sentences that move from lookup to returned data to optional wiki context, with no filler. Slightly dense and occasionally clausal ('otherwise a clear auction-only note'), but every sentence carries operational information.

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?

For a 7-parameter read tool with no output schema, the description adequately covers both the return payload and the main behavioral branches (bazaar vs BIN vs auction-only, candidate fallback, wiki augmentation). The main gap is that the ID-vs-search relationship and any mutual exclusivity are left unstated.

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 description coverage is 100%, so every parameter is already documented, making 3 the baseline. The description reinforces the conditional semantics of includeWiki and priceBasis ('used only for the lowest-BIN fallback') but adds little beyond what the schema text already states, and it never clarifies that itemId and search are alternative inputs or how maxCandidates interacts with resolution.

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 pairs a specific verb ('Look up') with a precise resource ('a single SkyBlock item by ID or name') and enumerates exactly what is returned: metadata (tier, category, stats, NPC price, museum/soulbound flags) plus a live value. It implicitly separates itself from siblings like skyblock_bazaar and skyblock_auctions by defining its output as bazaar data *or* a BIN fallback *or* an auction-only note, so an agent can distinguish it without opening the schema.

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?

It gives clear conditional guidance: use includeWiki when wiki context is wanted, ambiguous searches return candidates rather than a guess, and the BIN price only exists when an external source is configured. It stops short of explicitly naming alternatives (e.g. 'use skyblock_wiki_search for pure wiki queries' or 'use skyblock_bazaar for pure market queries'), so no exclusions are stated.

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