Skip to main content
Glama

Search merch

search_merch

Search the official Taren Raider merch store by product name and return matching products with their lowest price and buy link. Use this for any question about available shirts, stickers, or other merchandise.

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": {
      "query": "<query>"
    },
    "name": "search_merch"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesProduct name or keyword to search for, for example "tee" or "sticker".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the return shape (matches with lowest price and buy link), implying a read-only lookup, but says nothing about pagination, result limits, empty-result behavior, authentication, or rate limits. Adequate but incomplete for a no-annotation tool.

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?

Two sentences, purpose front-loaded, with the return payload stated up front. The second sentence is mildly redundant with the first (shirts/stickers are examples of product names) but does earn its place by enumerating merchandise categories.

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?

For a single-parameter lookup with no output schema, the description supplies the domain, the search semantics, and the return contents, which covers what an agent needs. It could add a note on result count or no-match behavior to be fully complete.

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% and the single query parameter is already documented with an example in the schema. The description restates the search-by-product-name semantics without adding format, matching, or syntax detail beyond the schema. Baseline 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?

States a specific verb (Search), the resource (official Taren Raider merch store), the search key (product name), and what is returned (matching products with lowest price and buy link). The sibling tools (vods, live status, schedule, site info) are in entirely different domains, so no differentiation is needed.

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?

"Use this for any question about available shirts, stickers, or other merchandise" gives clear positive usage context and implicitly bounds the tool away from the non-merch siblings. It stops short of naming an explicit alternative or exclusion rule, but the sibling set makes routing unambiguous.

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