Skip to main content
Glama
crithitstudio

hypixel-skyblock-mcp

Build SkyBlock Guide Context

skyblock_guide_context

Fetch Hypixel SkyBlock player profile, current mayor, and economy data to create tailored progression guidance.

Instructions

Fetch a profile plus current mayor and economy signals so an AI can write tailored SkyBlock progression advice. Requires HYPIXEL_API_KEY for player/profile data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidNoMinecraft UUID, dashed or undashed.
goalsNoGuide focus areas, for example mining, farming, dungeons, money.
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.
includeMayorNo
maxLoreLinesNo
selectedOnlyNoPrefer the selected profile when multiple profiles exist.
includeGardenNo
includeMuseumNo
includeRawNbtNoInclude simplified raw NBT for decoded sections. Very large output.
includeEconomyNo
memberUsernameNoCoop member username to inspect. Defaults to requested player.
decodeInventoriesNo
includeAllNbtDataNoSearch every base64 NBT payload on the member, not only inventory-like paths.
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 fully disclose behavioral traits. It mentions an API key requirement and implies data fetching, but does not specify rate limits, output size, error behavior, or side effects. For a composite tool with many parameters, this is insufficient transparency.

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 extremely concise with only two sentences. The first sentence captures the tool's purpose and outcome, and the second states a key prerequisite. No superfluous content; every sentence is essential.

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 (21 parameters, no output schema, many sibling tools), the description lacks crucial context such as output format, return structure, error cases, or size implications. An agent cannot fully anticipate the tool's behavior or integrate its output into a progression advice workflow from this description alone.

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 62%, and the description adds no extra meaning beyond the schema's parameter descriptions. The schema itself provides adequate descriptions for most parameters (e.g., 'goals' has a clear example), so baseline 3 is appropriate despite no added value from the description.

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's verb ('Fetch'), resource ('profile plus current mayor and economy signals'), and purpose ('so an AI can write tailored SkyBlock progression advice'). It distinguishes itself from sibling tools that focus on individual data sources (e.g., skyblock_profile, skyblock_bazaar) by combining multiple signals into a single context.

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 mentions a prerequisite (HYPIXEL_API_KEY) but does not provide explicit when-to-use or when-not-to-use guidance relative to sibling tools. It implies use for tailored advice but lacks exclusions or alternatives, leaving the agent to infer usage context.

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