Skip to main content
Glama
GlossMod

GlossModMCP

Official
by GlossMod

get_games

Search for games by name to retrieve their IDs and details, enabling further queries for mods and game information.

Instructions

获取游戏列表。

⚠️ 重要:这是所有游戏相关查询的入口点。必须先搜索游戏名称来获取 game_id,
然后才能在其他函数(如 get_mods)中使用该 ID。

典型工作流:
1. 使用 search 参数调用此函数来查找游戏
2. 从返回结果中获取游戏的 id 字段
3. 将该 id 作为 game_id 参数传递给 get_mods、get_game_detail 等函数

支持分页、搜索、类型筛选和排序。

参数:
- search: 游戏名称搜索关键词(必需用于查找特定游戏)
- game_type: 游戏类型筛选
- page: 页码
- page_size: 每页结果数

返回结构:
{
    "data": [
        {
            "id": number,                    # 游戏ID(用于其他查询)
            "game_name": string,             # 游戏名称
            "game_ename": string,            # 游戏英文名称
            "game_cover_imgUrl": string,     # 游戏封面图
            "game_path": string,             # 游戏路径
            "game_desc": string,             # 游戏描述
            "allcount": number,              # 总Mod数量
            "tcount": number                 # 最近30天Mod数量
        }
    ],
    "count": number,                         # 总数
    "page": number,                          # 当前页码
    "pageSize": number,                      # 每页数量
    "totalPages": number                     # 总页数
}

示例:
- 搜索 "Skyrim" 游戏 -> 获取 id = 123
- 搜索 Skyrim 的 Mod: get_mods(game_id=123)
- 或同时查询多个游戏: get_mods(game_id=[123, 456, 789])

游戏详细网址:  
https://mod.3dmgame.com/<game_path>
其中 game_path 来自返回结果中的 "game_path" 字段

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
searchNo
sort_byNoallcount
game_typeNo
page_sizeNo
sort_orderNodesc
Behavior5/5

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

No annotations exist, so the description fully bears the burden. It details pagination, search, filtering, sorting, and even provides the entire return structure. There are no hidden side effects; the tool is clearly read-only.

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 description is well-structured with clear sections (important note, workflow, parameters, return structure, example, URL). It is somewhat lengthy but every part adds value; front-loading of key info is good.

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?

Given no annotations and no output schema, the description covers all needed context: how to use the tool, what parameters do, the structure of the return data, and how to link results to sibling tools. It is complete for an agent to use correctly.

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?

With 0% schema description coverage, the description must explain parameters. It adequately describes search, game_type, page, and page_size. However, sort_by and sort_order are not explained, though their names are somewhat self-explanatory.

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 that the tool retrieves a list of games and is the entry point for game-related queries. It distinguishes itself from siblings like get_mods by explaining that the returned game_id is used in subsequent calls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit workflow: first use search to get a game_id, then use that ID in other functions. It gives examples and warns that this is the required entry point for game queries, making usage intentions very clear.

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/GlossMod/gloss-mod-mcp'

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