Skip to main content
Glama
crithitstudio

hypixel-skyblock-mcp

by crithitstudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get SkyBlock Garden

skyblock_garden
Read-onlyIdempotent

Fetch garden plot, commission, and composter data for a SkyBlock profile to monitor farming progress and composter status.

Instructions

Fetch garden plot, commission, and composter data for a SkyBlock profile.

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.
selectedOnlyNoPrefer the selected profile when multiple profiles exist.
memberUsernameNoCoop member username to inspect. Defaults to requested player.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.1.0
    • addedInput schema / properties / memberUsername / maxLength
      Added value: +64
    • removedInput schema / properties / memberUuid / minLength
      Removed value: -1
    • addedInput schema / properties / memberUuid / pattern
      Added value: +"^(?:[0-9a-f]{32}|[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12})$"
    • removedInput schema / properties / profileId / minLength
      Removed value: -1
    • addedInput schema / properties / profileId / pattern
      Added value: +"^(?:[0-9a-f]{32}|[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12})$"
    • addedInput schema / properties / profileName / maxLength
      Added value: +64
    • addedInput schema / properties / username / maxLength
      Added value: +64
    • removedInput schema / properties / uuid / minLength
      Removed value: -1
    • addedInput schema / properties / uuid / pattern
      Added value: +"^(?:[0-9a-f]{32}|[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12})$"
  2. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds nothing behavioral beyond that: no note on auth requirements, rate limits, or what happens with ambiguous profile selection. No contradiction with annotations, but no added value either.

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?

A single economical sentence with the resource list front-loaded and no filler. It is appropriately sized, though it could be slightly richer without becoming bloated.

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

Completeness3/5

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

With 7 parameters, no required fields, and no output schema, the description does list the three data categories returned, which partially compensates for the missing output schema. However, it does not explain selector behavior when no uuid/username is supplied or how multiple profiles are resolved, leaving the agent to infer resolution rules from the schema 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 100% across all 7 parameters, and each parameter carries a meaningful description (UUID format, username fallback, member vs. profile selectors, selectedOnly default). The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Fetch) plus the concrete resources it returns: garden plot, commission, and composter data, scoped to a SkyBlock profile. That is clear enough to distinguish it from siblings like skyblock_profiles or skyblock_inventory. It stops short of explicitly naming which sibling to prefer for related garden data, so 5 is not warranted.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives (skyblock_profile, skyblock_inventory, etc.), nor any prerequisites or exclusions. Usage is only implied by the resource name in the description.

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