Skip to main content
Glama

QuickMatch

Search QuickMatch AI game dev tools

search_tools
Read-only

Find AI tools for making video games in QuickMatch's checked list, filtered by category, engine, free plan, starting price and commercial use. Returns up to 10 tools with free plan, price, commercial-use terms, the date prices were checked and a quickmatch.si link. Commercial-use values are shown exactly as stored: yes, no, checking, n/a, limited, attribution.

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": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
freeNotrue: only tools with a free plan (the free plan line starts with "Yes"). false: only tools without one.
queryNoOptional words to match against tool names, what they are best for, summaries and features, e.g. "pixel art sprites".
engineNoGame engine the tool works in or exports to: godot, unity, unreal, roblox, gamemaker.
categoryNoTool category: maker (AI game makers), code (AI coding and engine assistants), art (2D art and sprites), 3d (3D models and worlds), anim (animation and mocap), music (music and sound effects), voice (voices and NPC dialogue), vibe (vibe-coding builders).
maxPriceNoHighest starting price (the tool's lowest listed paid plan, as a plain number in the vendor's own currency, which isn't always US dollars). Tools whose starting price is unlisted (null) or still "checking" are excluded when this is set.
commercialNotrue: only tools whose free plan allows commercial use (commercial.free is "yes"). Possible stored values: yes, no, checking, n/a, limited, attribution.

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/openWorld=false, so the description is free to spend its words on behavior: a hard result cap of 10, the fields returned (free plan, price, commercial terms, price-check date, link), and the exact stored commercial-use vocabulary. The remaining gap is that it does not say how results are ranked or whether the 10-item cap is truncation.

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 front-loaded sentences: the first covers purpose and filters, the second covers return shape and value encoding. No filler, and the result cap appears before the field list where an agent needs it.

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?

With no output schema, the description does the work of describing returned fields and the commercial-use vocabulary, and it explains the exclusion semantics for unlisted prices via the schema. It stops short of covering ordering, currency caveats, or whether the 10-item limit can be exceeded, which keeps it from being 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 coverage is 100% and two enums are fully spelled out in the schema, so the baseline of 3 applies. The description reinforces which dimensions can be filtered and clarifies that commercial-use values are returned verbatim, but adds little syntax or interpretation the schema does not already give.

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 AI tools for making video games") plus the exact source (QuickMatch's checked list) and the filter dimensions. It also says it returns up to 10 tools, which cleanly separates it from a single-item lookup like get_tool.

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?

Usage is implied by the filter list and the "Optional words" note in the schema, but the description never states when to prefer this over siblings such as compare_tools or get_tool, nor any when-not conditions. An agent can infer it is the discovery entry point, but only by inference.

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