Skip to main content
Glama
wzkzd666

wuwa-mcp

by wzkzd666
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

get_character_info

Fetch detailed Wuthering Waves character details—skills and build guides—as Markdown. Query a Chinese character name to receive complete, deduplicated data for LLM consumption.

Instructions

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

    Args:
        character_name: 要查询的角色的中文名称。

    Returns:
        包含角色信息的 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.9/5.0
Behavior4/5

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

No safety annotations are present, but the description goes beyond the tool name by specifying Markdown output, deduplication, no truncation, and error behavior – meaningful extra transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact, front-loaded purpose, and return behavior in two sentences. No filler or duplication of schema information beyond the useful Chinese-name constraint.

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

Completeness4/5

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

Covers input semantics, output format, dedup/no-truncation, and error result. Missing only an explicit call-to-action vs sibling get_character_profile.

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?

The schema only says 'character_name'; the description clarifies it must be the Chinese name, which is useful beyond the schema. It doesn't mention exact matching or alternatives, so not a 5.

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 a specific verb ('获取'), a precise resource (库街区 character info), and concrete content (skills, cultivation guides). It is clear enough to know what the tool returns, though it never explicitly contrasts itself with get_character_profile.

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?

It implies use when detailed character info is needed, but there is no explicit when-to-use/when-not-to-use guidance or mention of alternative tools.

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