Skip to main content
Glama
wzkzd666

wuwa-mcp

by wzkzd666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TRANSPORTNoTransport mode: 'stdio' for standard I/O (default) or 'http' for streamable HTTP.stdio

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_artifact_infoB

获取库街区上的声骸详细信息并以 Markdown 格式返回。

    参数：
        artifact_name: 要查询的声骸套装的中文名称。

    返回：
        包含声骸信息的 Markdown 字符串，
        或者在找不到声骸或获取数据失败时返回错误消息。
get_character_infoA

获取库街区上的角色详细信息包括角色技能，养成攻略等，并以 Markdown 格式返回。

    参数：
        character_name: 要查询的角色的中文名称。

    返回：
        包含角色信息的 Markdown 字符串（完整内容，只做去重、不截断），
        或者在找不到角色或获取数据失败时返回错误消息。
get_character_profileB

获取库街区上的角色档案信息并以 Markdown 格式返回。

    参数：
        character_name: 要查询的角色的中文名称。

    返回：
        包含角色档案信息的 Markdown 字符串，
        或者在找不到角色或获取数据失败时返回错误消息。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

TDQS

B3.4/5.0

Scored across 3 tools

Disambiguation3/5

get_character_info and get_character_profile both fetch character data by name, and the distinction (skills/guides vs profile/archive) is not immediately obvious from the names. get_artifact_info is clearly distinct, but the two character tools have overlapping boundaries that could cause misselection.

Naming Consistency5/5

All three tools follow the same get_<entity>_<type> snake_case pattern (get_artifact_info, get_character_info, get_character_profile). The convention is predictable and easy to parse.

Tool Count3/5

Three retrieval tools is thin for a game data server that likely has many entity types and would benefit from list/search operations. It covers only the most basic lookups, making the surface feel under-scoped.

Completeness2/5

There is no way to list or search for valid character or artifact names, so agents are stuck unless the user already knows exact Chinese names. Other game data (e.g. weapons) is absent, representing significant gaps for the domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources