Skip to main content
Glama
crithitstudio

hypixel-skyblock-mcp

Get SkyBlock Profile Context

skyblock_profile

Inspect a Hypixel SkyBlock profile: retrieves member skills, slayers, dungeons, pets, collections, currencies, accessories, and decoded inventories in compact JSON for AI processing.

Instructions

Fetch one SkyBlock profile and return compact AI-readable member context: skills, slayers, dungeons, pets, collections, currencies, accessories, and optional decoded inventories.

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.
profileNameNoCute profile name, for example Apple, Lemon, or Coconut.
maxLoreLinesNo
selectedOnlyNoPrefer the selected profile when multiple profiles exist.
includeGardenNoFetch garden data for the selected profile.
includeMuseumNoFetch museum data for the selected profile.
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. Large output.
decodeInventoriesNoDecode base64 gzipped NBT inventory sections when available.
includeAllNbtDataNoSearch every base64 NBT payload on the member, not only inventory-like paths.
includeRawProfileNoInclude the raw selected profile object. Large output.
includeItemDetailsNoInclude extra compact ExtraAttributes fields on decoded items.
maxInventorySectionsNo
maxItemsPerInventoryNo
inventorySectionPathsNoFilter decoded inventory sections by case-insensitive path substring, for example wardrobe_contents or backpack_contents.
inventorySectionTypesNoFilter 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.
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only mentions what it returns, not safety (e.g., read-only), rate limits, or authentication requirements. The description is not contradictory but lacks necessary behavioral context.

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?

The description is a single, front-loaded sentence that efficiently conveys the tool's core purpose and output. It avoids wordiness but could be slightly more structured with separate sentences for details.

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?

Despite having 20 parameters and no output schema, the description is brief and does not explain return format, error handling, or the meaning of 'compact AI-readable'. Important parameters like maxInventorySections and inventorySectionPaths lack context in the description.

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 85%, so the schema already documents most parameters. The description adds a high-level list of returned data but does not explain parameter interactions or specific effects beyond what the schema provides.

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 it fetches one SkyBlock profile and returns compact AI-readable member context with specific categories (skills, slayers, etc.), distinguishing it from sibling tools like skyblock_profiles which likely lists multiple profiles.

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 implies use for a full profile overview but does not explicitly state when to use alternatives like skyblock_garden or skyblock_inventory. No direct comparison or exclusions 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