Skip to main content
Glama
gooboot

MCP-BOS

by gooboot
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

server_info

Retrieve server information to monitor system status and configuration details for the MCP-BOS framework.

Instructions

获取服务器信息

Args: ctx: MCP上下文

Returns: dict: 服务器信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • core/server.py:73-89 (handler)
    The server_info tool handler function that returns server name, version, and list of loaded modules using config and registry.
    def server_info(ctx: Context) -> dict:
    """
    获取服务器信息

    Args:
        ctx: MCP上下文

    Returns:
        dict: 服务器信息
    """
    global_config = self.config_manager.get_global_config()

    return {
        "name": global_config.get('server_name', 'MCP Server'),
        "version": "1.0.0",
        "modules": self.registry.list_modules()
    }
  • core/server.py:72-72 (registration)
    The @self.server.tool() decorator registers the server_info function as an MCP tool.
    @self.server.tool()

Tool Definition Quality

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states that it returns server information as a dict, without disclosing behavioral traits like whether it's read-only, has side effects, requires authentication, or has rate limits. For a tool with zero annotation coverage, this is insufficient transparency.

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

Conciseness3/5

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

The description is brief but includes unnecessary structural elements like 'Args:' and 'Returns:' that don't add value beyond the schema. The core purpose is stated in one line, but the formatting could be more streamlined. It's not excessively verbose but has minor structural inefficiencies.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'server information' includes, the format of the dict return value, or any behavioral context. For a tool that presumably provides system-level data, more detail is needed to be fully useful to an AI agent.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information beyond what the schema provides, but with no parameters, a baseline of 4 is appropriate as there's nothing to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states '获取服务器信息' (get server information), which provides a basic verb+resource purpose. However, it's vague about what specific server information is retrieved and doesn't differentiate from sibling tools like 'hello' or 'my_tool'. The purpose is clear but lacks specificity and sibling differentiation.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention any context, prerequisites, or exclusions for usage. With sibling tools like 'add', 'hello', and 'my_tool' available, there's no indication of when this specific tool is appropriate.

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/gooboot/MCP-BOS'

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