Skip to main content
Glama
wzkzd666

wuwa-mcp

by wzkzd666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_character_info

Query Wuthering Waves character details like skills and build guides by Chinese name, returning deduplicated Markdown for LLM use.

Instructions

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

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
character_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful runtime behavior: output is a Markdown string, content is returned in full (deduplicated but never truncated), and an error message is returned when the character is missing or the fetch fails. It omits auth/rate-limit or source-freshness details, but the failure-mode and completeness disclosure is well beyond what the schema provides.

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?

Front-loads the purpose, then cleanly separates 参数 and 返回 sections. There is minor redundancy in restating the Markdown return twice, but overall it is tight and well organized.

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

Completeness3/5

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

Return values are largely covered by the output schema, and error behavior is documented, but the description never addresses sibling selection against get_character_profile, which is the single biggest ambiguity an agent faces with this tool.

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 0%, so the description must compensate, and it does: it states that character_name is the Chinese name of the character, a non-obvious constraint on the value format that the schema's bare 'string' type does not convey.

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?

Names a specific verb (获取) and resource (角色详细信息), and enumerates the content retrieved (角色技能、养成攻略) plus the output format (Markdown). However, it does nothing to distinguish itself from the very similar sibling get_character_profile, so an agent cannot tell the two apart from the text alone.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of the closely-named alternative get_character_profile. The agent is left to guess which of the two character tools to call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools