Skip to main content
Glama

hp_by_house

Read-onlyIdempotent

List characters belonging to a chosen Hogwarts house by providing the house name (Gryffindor, Slytherin, Hufflepuff, or Ravenclaw).

Instructions

List characters by Hogwarts house.

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": "<house>"
    },
    "name": "hp_by_house"
  }
}

Input Schema

NameRequiredDescriptionDefault
houseYesHouse name: gryffindor, slytherin, hufflepuff, or ravenclaw

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

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, openWorldHint, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — no return shape, no note on whether house matching is case-sensitive or how many results to expect.

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 front-loaded sentence with no filler. Its brevity is efficient rather than padded, though it is arguably under-specified for the job it must do.

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?

For a one-parameter read tool with complete annotations and a fully documented schema, this is close to adequate. However, it says nothing about the response (list shape, character fields, ordering), and with no output schema that information would have been valuable.

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%; the 'house' parameter already lists the four allowed values. The description restates the same fact ('by Hogwarts house') without adding format, case, or behavior details, so 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?

States a specific verb ('List') and resource ('characters') with a clear filter ('by Hogwarts house'). It does not distinguish itself from sibling tools like hp_all_characters, hp_students, or hp_staff, which appear to overlap heavily.

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 guidance on when to use this versus hp_all_characters (unfiltered listing) or hp_students/hp_staff. The agent must infer that this is the house-filtered variant purely from the name.

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