Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

join_hypesquad_house

Join a Discord HypeSquad house by supplying its ID—1 for Bravery, 2 for Brilliance, 3 for Balance—to set your account's HypeSquad membership.

Instructions

Join a HypeSquad house: 1 Bravery, 2 Brilliance, 3 Balance. [POST /hypesquad/online]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "house_id": "<house_id>"
    },
    "name": "join_hypesquad_house"
  }
}

Input Schema

NameRequiredDescriptionDefault
house_idYeshouse id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this is a non-destructive external write. The description adds the HTTP endpoint and the house-id mapping but says nothing about whether joining replaces a prior house or what side effects occur on the account.

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?

A single front-loaded line with the code mapping and endpoint; there is no filler and nothing is buried. The most decision-relevant information (valid values) comes before the endpoint tag.

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 one-parameter, non-destructive write with no output schema and covered annotations, the definition gives enough to invoke it correctly. The only real gap is the absence of any statement about interaction with an existing house membership.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the schema only says "house id" while the description supplies the actual value-to-house mapping (1/2/3), which is meaningful semantics the schema lacks. That is genuine added value above the baseline 3 for fully documented schemas.

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?

"Join a HypeSquad house" states a specific verb and resource, and the numbered list (1 Bravery, 2 Brilliance, 3 Balance) makes the operation concrete. It is clearly the inverse of the sibling leave_hypesquad_house, though the description itself does not name that sibling.

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?

Usage is implied rather than explained: the enum mapping tells an agent what to pass, but there is no guidance on when joining is appropriate, whether an existing house must be left first, or what happens if the user is already in a house.

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