Skip to main content
Glama
funinii

TrendRadar

by funinii

get_system_status

Monitor system health and operational metrics for TrendRadar, including version details, data statistics, and cache status.

Instructions

获取系统运行状态和健康检查信息

返回系统版本、数据统计、缓存状态等信息

Returns: JSON格式的系统状态信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler implementation for the `get_system_status` tool within the `SystemManagementTools` class. It fetches the status from the `data_service` and returns it with a success flag or handles exceptions.
    def get_system_status(self) -> Dict:
        """
        获取系统运行状态和健康检查信息
    
        Returns:
            系统状态字典
    
        Example:
            >>> tools = SystemManagementTools()
            >>> result = tools.get_system_status()
            >>> print(result['system']['version'])
        """
        try:
            # 获取系统状态
            status = self.data_service.get_system_status()
    
            return {
                **status,
                "success": True
            }
    
        except MCPError as e:
            return {
                "success": False,
                "error": e.to_dict()
            }
        except Exception as e:
            return {
                "success": False,
                "error": {
                    "code": "INTERNAL_ERROR",
                    "message": str(e)
                }
            }
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 implies a read-only operation by stating it '获取' (gets) information and returns JSON, but doesn't disclose behavioral traits like whether it requires authentication, has rate limits, affects system performance, or provides real-time vs. cached data. The description adds basic context (what it returns) but lacks critical operational details for a tool with no annotations.

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 concise and front-loaded, starting with the core purpose in the first line. It uses three short sentences (in Chinese and English) that efficiently cover what the tool does and returns. There's minimal waste, though the bilingual format adds slight redundancy.

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?

Given 0 parameters, 100% schema coverage, and an output schema (implied by 'Has output schema: true'), the description doesn't need to explain parameters or return values. However, as a system status tool with no annotations, it should provide more context on usage scenarios or behavioral aspects (e.g., when to call it, what '健康检查' entails). It's adequate but has gaps in guidance and transparency.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. Baseline is 4 for 0 parameters, as it avoids unnecessary repetition and focuses on the tool's function.

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: '获取系统运行状态和健康检查信息' (get system running status and health check information) and specifies what it returns ('系统版本、数据统计、缓存状态等信息' - system version, data statistics, cache status, etc.). It distinguishes from siblings like get_current_config (likely configuration) or get_latest_news (news content). However, it doesn't explicitly contrast with all siblings, keeping it at 4 rather than 5.

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. It doesn't mention scenarios like system monitoring, debugging, or health checks, nor does it reference sibling tools like get_current_config (which might overlap with configuration aspects) or trigger_crawl (which might affect system status). Without any usage context, it scores low.

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/funinii/TrendRadar'

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