Skip to main content
Glama

get_character_info

Retrieve detailed character information from Wuthering Waves including skills and cultivation guides in Markdown format for game strategy planning.

Instructions

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

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
character_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary MCP tool handler for 'get_character_info', registered via @mcp.tool() decorator. It handles input validation implicitly via type hints, calls the character service, and provides error messages.
    @mcp.tool()
    async def get_character_info(character_name: str) -> str:
        """获取库街区上的角色详细信息包括角色技能,养成攻略等,并以 Markdown 格式返回。
    
        Args:
            character_name: 要查询的角色的中文名称。
    
        Returns:
            包含角色信息的 Markdown 字符串,
            或者在找不到角色或获取数据失败时返回错误消息。
        """
        try:
            character_service, _ = get_services()
            return await character_service.get_character_info(character_name)
        except (DataNotFoundException, ServiceException) as e:
            # These exceptions already have user-friendly messages
            return str(e)
        except Exception:
            return f"错误:处理 '{character_name}' 时发生意外错误。请检查服务器日志。"
  • Interface protocol defining the expected signature for get_character_info: input character_name (str), output str (markdown). Serves as schema reference.
    async def get_character_info(self, character_name: str) -> str:
        """Get comprehensive character information."""
        ...
  • Manual registration and dispatch for 'get_character_info' tool in the HTTP transport mode endpoint.
    if tool_name == "get_character_info":
        result = await character_service.get_character_info(arguments.get("character_name"))
  • The CharacterService implementation providing the core business logic for fetching, parsing, and formatting character information into Markdown, including optional strategy content.
    async def get_character_info(self, character_name: str) -> str:
        """Get comprehensive character information including strategy.
    
        Args:
            character_name: Name of the character to query.
    
        Returns:
            Markdown formatted character information.
    
        Raises:
            ServiceException: If character retrieval fails.
        """
        try:
            self.logger.info(f"Getting character info for: {character_name}")
    
            # Get character raw data
            character_raw_data = await self._get_character_data(character_name)
    
            # Extract strategy item ID for parallel processing
            strategy_item_id = self._extract_strategy_item_id(character_raw_data)
    
            # Parallel processing: parse profile and fetch strategy
            profile_task = asyncio.create_task(
                asyncio.to_thread(self.content_parser.parse_main_content, character_raw_data)
            )
    
            strategy_task = None
            if strategy_item_id:
                strategy_task = asyncio.create_task(self._fetch_strategy_content(strategy_item_id))
    
            # Wait for profile parsing
            character_profile_data = await profile_task
    
            # Generate markdown for profile
            character_markdown = self.markdown_service.generate_character_markdown(
                character_profile_data, include_strategy=False
            )
    
            # Process strategy if available
            strategy_markdown = ""
            if strategy_task:
                try:
                    strategy_raw_data = await strategy_task
                    if strategy_raw_data:
                        strategy_parsed = await asyncio.to_thread(
                            self.content_parser.parse_strategy_content, strategy_raw_data
                        )
                        strategy_markdown = self.markdown_service.generate_strategy_markdown(strategy_parsed)
                except Exception as e:
                    self.logger.warning(f"Failed to process strategy content: {e}")
    
            # Combine results
            combined_markdown = character_markdown
            if strategy_markdown:
                combined_markdown += "\n\n" + strategy_markdown
    
            # Add strategy link if available
            if strategy_item_id:
                link_markdown = self._generate_strategy_link_markdown(strategy_item_id)
                combined_markdown += "\n\n" + link_markdown
    
            self.logger.info(f"Successfully generated character info for: {character_name}")
            return combined_markdown
    
        except DataNotFoundException:
            error_msg = f"Character '{character_name}' not found"
            self.logger.error(error_msg)
            return f"错误:未找到名为 '{character_name}' 的角色。"
    
        except Exception as e:
            self.logger.error(f"Failed to get character info for {character_name}: {e}")
            raise ServiceException(f"Character info retrieval failed: {e}")
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the output format (Markdown) and error handling (returns error message if character not found or data retrieval fails), which adds useful context beyond basic functionality. However, it doesn't cover rate limits, authentication needs, or other operational traits.

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?

The description is appropriately sized and front-loaded, with the core purpose stated first. The Args and Returns sections are structured but slightly verbose; every sentence earns its place by providing essential details like output format and error handling, though it could be more streamlined.

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?

Given the tool's moderate complexity (1 parameter, no annotations, but with output schema), the description is fairly complete. It explains the purpose, parameter semantics, output format, and error handling. The presence of an output schema means it doesn't need to detail return values, but it could benefit from more usage guidelines to address sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant meaning beyond the input schema, which has 0% description coverage. It specifies that 'character_name' must be the Chinese name of the character, clarifying language and format requirements not evident from the schema alone. This compensates fully for the schema's lack of documentation.

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 clearly states the tool's purpose: to retrieve detailed character information including skills and cultivation guides from '库街区' (likely a game or platform). It specifies the verb '获取' (get/retrieve) and resource '角色详细信息' (character details), but doesn't explicitly differentiate from sibling tools like 'get_character_profile' which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_character_profile' or 'get_artifact_info'. It mentions the parameter 'character_name' but doesn't explain context, prerequisites, or exclusions for usage. The agent must infer usage from the purpose alone.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jacksmith3888/wuwa-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server