Skip to main content
Glama
lieyanqzu
by lieyanqzu

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_card_by_set_and_numberB

通过系列代码和收集编号获取单张卡牌。

search_cardsA

通过查询字符串搜索卡牌,支持分页和排序。

查询语法示例:

  • t:creature c:r (红色生物)

  • pow>=5 or mv<2 (力量大于等于5或法术力值小于2)

  • o:"draw a card" -c:u (包含"抓一张牌"的非蓝色牌)

  • (t:instant or t:sorcery) mv<=3 (3费或以下的瞬间或法术)

分页参数:

  • page: 页码 (整数, 默认 1)

  • page_size: 每页数量 (整数, 默认 20, 最大 100)

排序参数:

  • order: 按字段排序,逗号分隔。前缀 - 表示降序 (例如: name, -mv, name,-rarity) 默认排序: name

其他参数:

  • unique: 去重方式 (id, oracle_id, illustration_id)

  • priority_chinese: 是否优先显示中文卡牌

get_setsB

返回所有MTG卡牌系列的完整数据,按发布日期降序排列

get_setB

根据系列代码获取单个系列的详细信息

get_set_cardsA

获取特定系列的所有卡牌,支持分页和排序。

hzlsB

活字乱刷(使用卡牌图像拼接句子),将输入的文本使用魔法卡牌图像拼接成图片

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have distinct purposes: get_card_by_set_and_number retrieves a specific card, get_set and get_set_cards handle series data, get_sets lists all series, and search_cards performs general searches. However, get_set_cards and search_cards could be confused as both retrieve card lists, though their scopes differ (series-specific vs. general).

Naming Consistency4/5

Tools follow a consistent verb_noun pattern (e.g., get_card_by_set_and_number, get_set, get_set_cards, get_sets, search_cards), which is clear and predictable. The exception is 'hzls', which uses an acronym and lacks a verb, slightly deviating from the pattern but not severely impacting readability.

Tool Count5/5

With 6 tools, the server is well-scoped for Magic: The Gathering card data management. Each tool serves a specific function (e.g., retrieving cards, series, or generating images), and there are no redundant or missing tools for the apparent domain, making the count appropriate.

Completeness4/5

The tool surface covers core operations for MTG data: retrieving cards (by ID, series, or search), series information, and a creative image tool. Minor gaps exist, such as no explicit update or delete tools for data modification, but this is reasonable for a read-focused API, and agents can work around it with the provided search and retrieval functions.

Maintenance

ActivityInactive
ResponsivenessUnresponsive