Skip to main content
Glama

hello

Generate personalized greeting messages by providing a name parameter. This MCP-BOS tool returns customized welcome text for AI applications.

Instructions

返回问候消息

Args: name: 要问候的名称

Returns: str: 问候消息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoWorld

Implementation Reference

  • The handler function for the 'hello' tool. Decorated with @server.tool(), it takes a name parameter (default 'World') and returns a formatted greeting message from the module config.
    @server.tool()
    def hello(name: str = "World") -> str:
        """
        返回问候消息
    
        Args:
            name: 要问候的名称
    
        Returns:
            str: 问候消息
        """
        message = self.config.get('message', 'Hello, {}!')
        return message.format(name)
Behavior2/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 of behavioral disclosure. It states the tool returns a greeting message as a string, but doesn't describe any behavioral traits such as side effects, error handling, or performance characteristics. For a simple tool, this might be minimal, but it lacks details like whether it's idempotent or has any constraints.

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 structured with clear sections for Args and Returns, using minimal text. It avoids unnecessary details, making it easy to scan. However, it could be more front-loaded by stating the purpose more prominently before the parameter details.

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 the tool's low complexity (one optional parameter, no output schema, no annotations), the description is somewhat complete but has gaps. It explains the basic input and output, but lacks usage context and behavioral details. For a simple greeting tool, this might be adequate, but it doesn't fully cover all aspects needed for optimal agent invocation.

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

Parameters3/5

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

The description adds that the parameter 'name' is '要问候的名称' (the name to greet), which provides basic semantic meaning. However, with 0% schema description coverage and only one parameter documented in the description, it partially compensates but doesn't fully explain the default value 'World' or any validation rules. The baseline is 3 since the schema covers the parameter structure, but the description adds limited value.

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 the tool '返回问候消息' (returns a greeting message), which clearly indicates its purpose. However, it doesn't specify the exact format or content of the greeting beyond returning a string, and it doesn't differentiate from sibling tools like 'add' or 'my_tool' which have unrelated functions. The purpose is understandable but somewhat vague in execution details.

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 any context, prerequisites, or exclusions for usage. Given that sibling tools include 'add' (likely for arithmetic) and 'my_tool' (unspecified), there's no indication of when a greeting tool is appropriate versus other operations.

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