Skip to main content
Glama

QuickMatch

Find agent skills and MCP servers for game dev

find_skills
Read-only

Find agent skills and MCP servers for game development listed on QuickMatch, filtered by kind, coding agent, engine and words. Returns up to 10 with agents, engines, license, cost, last update and a quickmatch.si link.

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_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNomcp: MCP servers. skill: agent skills and plugins.
agentNoCoding agent or client, matched ignoring case and punctuation ("claude-code" matches "Claude Code"). Entries that work with "Any MCP client" match every agent. Values in the list: Antigravity, Any MCP client, Claude API, Claude Code, Claude Desktop, Claude.ai, Cline, Codex, Cursor, Devin Desktop (Windsurf), Devin Desktop/Windsurf, Gemini, Gemini CLI, GitHub Copilot, Google Antigravity, Grok, Hermes, Kilo Code, Kimi Code, Kiro, LM Studio, OpenCode, Pi, Rider, Trae, Unity AI Gateway, VS Code, Windsurf.
queryNoOptional words to match against names, summaries, features and engines, e.g. "sprites" or "blueprints".
engineNoEngine or tool, matched the same way ("godot" matches "Godot 4.7+"). Values in the list: aseprite, babylon-js, bethesda, bevy, blender, blockbench, effekseer, engine-agnostic, flame, gamemaker, godot, higgsfield-web-game-template, littlejs, love, maya, melonjs, minecraft, net-xna, p, phaser, pixijs, pygame, roblox, shadertoy, source, three-js, three-js-r, unity, unreal-engine, web, webgl, webgpu, zbrush.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds two useful behavioral facts: results are capped at 10 and each result carries agents, engines, license, cost, last update and a quickmatch.si link. It still says nothing about behavior on zero matches or ordering/ranking of results.

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 tightly written sentences with the purpose front-loaded and the return shape second; no filler. It is slightly dense in the second sentence but every clause conveys information an agent can use.

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 compensates by enumerating the returned fields and the result cap. All four parameters are fully documented by the schema, so the only remaining gaps are minor (result ordering, empty-result behavior) for what is a simple read-only search tool.

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 the schema already documents each parameter, including enum values and normalized matching rules for agent and engine. The description's 'filtered by kind, coding agent, engine and words' merely restates the parameter set and adds no new semantics, so the baseline 3 applies.

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?

States a specific verb (find) and concrete resources (agent skills and MCP servers for game development) on a named catalog (QuickMatch), so the agent knows exactly what it retrieves. It does not explicitly contrast itself with the sibling tools (search_tools, get_tool, compare_tools), leaving that distinction to be inferred from the domain-specific framing.

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 by naming the filterable dimensions (kind, coding agent, engine, words) and the 10-result cap, which hints at a discovery use case. However, it gives no explicit when-to-use / when-not-to-use guidance and never points to an alternative tool.

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