Skip to main content
Glama

Mhw

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Monsters

get_monsters
Read-onlyIdempotent

Search Monster Hunter World monsters by name, species, or size class. Returns species classification, elements, ailments, and weaknesses to plan hunts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by monster name (case-insensitive substring), e.g. "nergigante".
typeNoSize class: "large" (hunt targets) or "small" (ambient wildlife).
limitNoMaximum number of monsters to return. Defaults to 20.
speciesNoFilter by species. One of: elder dragon, flying wyvern, brute wyvern, bird wyvern, fanged wyvern, piscine wyvern, fanged beast, neopteron, herbivore, wingdrake, relict, fish.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes
total_matchedNoMonsters matching the filters before the limit cut.
total_monstersNoTotal monsters in the MHW database.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / total_matched
      Added value: +{
+  "description": "Monsters matching the filters before the limit cut.",
+  "type": "integer"
+}
    • addedOutput schema / properties / total_monsters
      Added value: +{
+  "description": "Total monsters in the MHW database.",
+  "type": "integer"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Filter by monster name (case-insensitive substring), e.g. \"nergigante\".",
+  "type": "string"
+}
    • addedInput schema / properties / species
      Added value: +{
+  "description": "Filter by species. One of: elder dragon, flying wyvern, brute wyvern, bird wyvern, fanged wyvern, piscine wyvern, fanged beast, neopteron, herbivore, wingdrake, relict, fish.",
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Size class: \"large\" (hunt targets) or \"small\" (ambient wildlife).",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "description": "Monster data from MHW database",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10
+  },
+  {
+    "limit": 20
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value by disclosing what data is returned (species classification, elements, ailments, weaknesses), which goes beyond the safety annotations. No contradictions exist.

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 two sentences, front-loaded with the action and resource, and every clause contributes necessary information. No filler or repetition.

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

Completeness5/5

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

With a robust schema and rich annotations, the description sufficiently completes the picture by stating the return fields and the planning use case. An output schema exists, so return value details are not needed 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 100% for all four parameters, so the schema fully documents name, type, limit, and species. The description only summarizes these filters without adding new details, thus the baseline of 3 applies.

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 uses a specific verb ('Search') and identifies the resource ('Monster Hunter World monsters') with clear filter dimensions (name, species, size class). It distinguishes itself from sibling get_* tools by focusing solely on monsters and their stats.

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

Usage Guidelines4/5

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

The description states the use case ('to plan hunts') and what filters can be applied, providing clear context for when to use this tool. However, it does not explicitly mention alternatives or when not to use it, though the resource distinction makes the intended usage obvious.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mhw toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources