Skip to main content
Glama
ArtSabintsev

Guild Wars 1 MCP

by ArtSabintsev

Search r/GuildWars

gw1_subreddit_search

Find posts on the r/GuildWars subreddit by keyword. Adjust sort and result count to refine your search.

Instructions

Search r/GuildWars public Atom results. Author/handle fields are omitted unless includeAuthors is true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNonew
limitNo
queryYes
maxCharactersNo
includeAuthorsNo
Behavior3/5

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

The description discloses that author fields are conditionally included and that results are in Atom format, adding behavioral context beyond the schema. However, it does not cover other behavioral aspects like rate limits, pagination, or validation rules.

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?

Two sentences with no extraneous information. The key behavioral constraint (author omission) is front-loaded.

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

Completeness2/5

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

Given 5 parameters with no schema descriptions, no output schema, and no annotations, the description is insufficient. It does not describe the return value format or the impact of parameters like sort and limit.

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

Parameters2/5

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

With 0% schema description coverage, the description only adds meaning for the includeAuthors parameter. It does not explain sort, limit, maxCharacters, or the nature of the query parameter, leaving significant gaps.

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 clearly states the tool searches r/GuildWars using public Atom results and specifies that author fields are omitted unless includeAuthors is true. It effectively distinguishes from sibling tools like gw1_builds_search and gw1_content_search.

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?

The description implies usage for subreddit searching but does not explicitly state when to use this tool versus alternatives. No exclusions or context for when-not to use are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ArtSabintsev/guildwars1-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server