Skip to main content
Glama

find_quest

Read-only

Look up a Warcraft Wiki quest page by quest ID to avoid title searches that return the Retail page instead of Classic/Forever.

Instructions

Find the Warcraft Wiki page of a quest from its quest ID.

Use this instead of searching the quest title: Forever reuses Classic quests (same ID), and a title search often finds the Retail page, which has other NPCs and rewards. character_status shows each quest as "(quest 365)". Then call read_wiki_page with the title it returns. If several pages are listed, read the one for Classic or Forever. Always cite the link you used.

Args: quest_id: The quest ID, for example 365.

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": {
      "quest_id": "<quest_id>"
    },
    "name": "find_quest"
  }
}

Input Schema

NameRequiredDescriptionDefault
quest_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the description adds value rather than repeating safety info: it discloses that results can be ambiguous (several pages listed) and supplies a disambiguation rule plus a citation obligation. It doesn't say what happens for an unknown or invalid quest ID, which is the main remaining behavioral gap.

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?

Front-loaded with the core purpose, then the disambiguation rationale, then the next step and citation rule. Dense and mostly waste-free, though the rationale about Retail vs Classic rewards runs slightly long for a single-parameter lookup.

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?

An output schema exists, so return formatting need not be explained; the description correctly spends its words on the ambiguous cases (multiple pages) and the downstream workflow. Adding invalid-ID behavior would make it fully complete for a lookup tool of this complexity.

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 0% for the single parameter, so the description must carry the meaning — and it does, giving an example value (365) and, importantly, telling the agent where the ID comes from: character_status shows each quest as "(quest 365)". It stops short of stating the expected range or error behavior for non-existent IDs.

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?

States a specific verb and resource ("Find the Warcraft Wiki page of a quest") plus the exact identifying input (quest ID). It also explicitly distinguishes itself from title-based searching, so an agent can separate it from search_wiki without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative it replaces ("Use this instead of searching the quest title") and explains the concrete failure mode of that alternative (Retail vs Classic/Forever pages with different NPCs and rewards). It also gives the follow-up step: call read_wiki_page with the returned title, and prefer the Classic/Forever page when multiple are listed.

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