Skip to main content
Glama
wzkzd666

wuwa-mcp

by wzkzd666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_character_profile

Fetch Wuthering Waves character profile details by Chinese name and return them as Markdown, or an error when the character cannot be found or data fails.

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

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return format (Markdown) and the failure behavior (returns an error message when the character is not found or fetching fails), which is useful. It does not state whether data is fetched live, whether any authentication or rate limits apply, or the freshness/incompleteness of profiles.

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-loaded with the core purpose followed by clearly labelled parameter and return sections. No wasted sentences, though the return-value section partly duplicates what the existing output schema already expresses.

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?

The output schema already covers return values, so re-explaining them in prose is mild redundancy rather than a gap. The real shortfall is the absence of any routing guidance distinguishing this tool from get_character_info, which is the main thing an agent needs here.

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 identifies the single parameter as the character's Chinese name. The 'Chinese name' constraint is meaningful because it hints that non-Chinese names/aliases will not resolve, something the bare string schema 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?

States a specific verb and resource (retrieve character profile from 库街区) plus the output format (Markdown), which is concrete. However it offers no differentiation from the sibling get_character_info, leaving the agent unable to tell which of the two near-identical-sounding tools to pick.

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?

There is no when-to-use guidance and no mention of alternatives. With siblings named get_character_info and get_artifact_info, the description should have said how get_character_profile differs, but it gives none.

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