Skip to main content
Glama

QuickMatch

Get one QuickMatch tool

get_tool
Read-only

Full QuickMatch details for one AI game dev tool: summary, features, free plan, price, starting price, commercial-use terms, engines, exports, the vendor pricing page and the date it was checked. Values are exactly as stored ("checking" means not confirmed yet). Commercial-use values are shown exactly as stored: yes, no, checking, n/a, limited, attribution. Unknown names return the 5 closest tools.

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": {
      "tool": "<tool>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool slug from a quickmatch.si/tools/<slug>/ link (like "pixellab"), or the exact tool name (any case).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), yet the description still adds real behavioral context: values are returned exactly as stored, "checking" is a status not a confirmed value, and commercial-use can be one of six literal values. It also discloses the fuzzy fallback that returns the 5 closest tools for unknown names—genuinely useful behavior not visible in the annotations.

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?

The definition is front-loaded with what is returned and follows with value-semantics caveats and the fallback, with no filler sentences. The long field enumeration is dense but each item maps to actual returned data, so it earns its space.

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

Completeness5/5

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

This is a single-parameter read-only lookup with no output schema, so the description must carry the return-shape burden—and it does, listing returned fields and clarifying status literals and the unmatched-input fallback. Nothing an agent needs in order to call it correctly is missing.

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 100%, so the slug-or-exact-name contract is already documented. The description nonetheless adds meaning beyond the schema by specifying what happens when the supplied name matches nothing—the 5 closest tools are returned—which tells the agent how to interpret an ambiguous or misspelled input.

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?

The description names the resource precisely ("Full QuickMatch details for one AI game dev tool") and enumerates the returned fields—summary, features, free plan, price, commercial-use terms, engines, exports, pricing page, check date—so an agent knows exactly what payload to expect. It does not explicitly contrast itself with siblings like search_tools or compare_tools, which keeps it from a 5.

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 only implied: the tool is for fetching a single known tool, and the unknown-name fallback hints at recovery when an identifier is wrong. There is no explicit "use search_tools first to find a slug" or "use compare_tools for side-by-side" routing, so the agent must infer the boundary from the sibling names alone.

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