Skip to main content
Glama
crithitstudio

hypixel-skyblock-mcp

Get SkyBlock Inventory Sections

skyblock_inventory

Fetch and decode inventory-like NBT sections for a Hypixel SkyBlock profile, including wardrobe, armor, ender chest, backpacks, and more. Use filters to focus on specific sections.

Instructions

Fetch and decode inventory-like NBT sections for one SkyBlock profile, including wardrobe, armor, equipment, ender chest, backpacks, vault, and bags. Use filters to keep output focused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidNoMinecraft UUID, dashed or undashed.
usernameNoMinecraft username. Use this when the user gives a name.
profileIdNoSpecific SkyBlock profile UUID.
memberUuidNoCoop member UUID to inspect. Defaults to requested player.
maxSectionsNo
profileNameNoCute profile name, for example Apple, Lemon, or Coconut.
maxLoreLinesNo
sectionPathsNoFilter decoded inventory sections by case-insensitive path substring, for example wardrobe_contents or backpack_contents.
sectionTypesNoFilter decoded inventory sections by type. Common values: inventory, wardrobe, armor, equipment, ender_chest, backpack, accessory_bag, potion_bag, fishing_bag, quiver, personal_vault, sack, loadout, container, unknown. Omit or include all for all inventory-like sections.
selectedOnlyNoPrefer the selected profile when multiple profiles exist.
includeRawNbtNoInclude simplified raw NBT for decoded sections. Very large output.
memberUsernameNoCoop member username to inspect. Defaults to requested player.
includeRawMemberNoInclude the raw selected member object. Very large output.
includeAllNbtDataNoSearch every base64 NBT payload on the member, not only inventory-like paths.
includeItemDetailsNoInclude extra compact ExtraAttributes fields on decoded items.
maxItemsPerSectionNo
Behavior2/5

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

No annotations exist, so the description must carry the full burden. It does not disclose any behavioral traits such as rate limits, authentication needs, potential for large responses, or side effects. The only behavioral hint is the ability to filter, but the tool's impact (e.g., API cost) is unmentioned.

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?

The description is two sentences: the first clearly states the tool's purpose, the second gives a concise usage tip. No extraneous information; every sentence earns its place.

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

Completeness2/5

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

Given the tool's complexity (16 parameters, no output schema, no annotations), the description is incomplete. It fails to describe the return format, potential for large output, or any constraints. The agent lacks context to correctly handle the tool's response.

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 high (81%). The description lists section types that overlap with the schema's 'sectionTypes' parameter description, adding minimal new meaning. The baseline 3 applies as the schema already documents parameters well.

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 fetches and decodes inventory-like NBT sections for a SkyBlock profile, listing specific sections (wardrobe, armor, etc.). It distinguishes from sibling tools like skyblock_profile or decode_skyblock_nbt by focusing solely on inventory contents.

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

Usage Guidelines3/5

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

The description advises using filters to keep output focused, but does not explicitly state when to use this tool vs alternatives (e.g., skyblock_profile for general profile data). No when-not-to-use guidance or comparisons to siblings are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/crithitstudio/hypixel-skyblock-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server