Skip to main content
Glama

Find games Wilderack hosts

find_games
Read-onlyIdempotent

The games Wilderack hosts, or the ones matching a name: whether each is for sale now, starting soon or coming soon, its editions, mods, crossplay and the plan Wilderack suggests. No account needed. Use it first when someone asks where to host a game server.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoA game name, such as "minecraft" or "terraria". Leave out for every game.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior. The description adds useful context beyond the schema: it discloses that no account is needed and enumerates the return fields (sale status, editions, mods, crossplay, plan suggestion) without an output schema. It does not cover rate limits or error behavior, but for a simple read-only catalog tool this is sufficient.

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?

The description is front-loaded with the core purpose and return attributes, followed by a short usage cue. It is dense but every sentence contributes; the first sentence is long and list-like but not wasteful. Slightly better structural separation would merit a 5.

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?

For a simple catalog tool with one optional parameter and no output schema, the description fully covers purpose, return content, authentication needs, and primary usage. Nothing critical an agent needs in order to call it correctly is missing.

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%, so the single optional query parameter is already documented with a name, max length, and examples. The description adds only a light restatement of filtering by name ('the ones matching a name'), which is implicit in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the resource (games Wilderack hosts) and the scope (all hosted games or those matching a name), plus what attributes are returned (sale status, editions, mods, crossplay, suggested plan). It does not explicitly differentiate itself from siblings like get_game or get_prices, but 'Use it first' helps establish its role as the entry point.

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 final sentence gives clear when-to-use guidance: 'Use it first when someone asks where to host a game server.' It does not name alternatives or state when not to use this tool, but the context is strong enough for an agent to infer it should be the starting point for broad game-hosting questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources