Skip to main content
Glama
dh1789

My First MCP

by dh1789

get_server_info

Retrieve server information and available tools from the My First MCP tutorial server for basic utility operations.

Instructions

이 MCP 서버의 정보와 사용 가능한 Tool 목록을 반환합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function implementing the get_server_info tool logic. Returns a ServerInfo object containing server name, version, description, and list of available tools.
    export function getServerInfo(): ServerInfo {
      return {
        name: "my-first-mcp",
        version: "1.0.0",
        description: "MCP 서버 개발 튜토리얼 - 첫 번째 MCP 서버",
        tools: [
          "get_current_time - 현재 시간 조회",
          "calculate - 사칙연산 계산기",
          "get_random_number - 랜덤 숫자 생성",
          "reverse_string - 문자열 뒤집기",
          "get_server_info - 서버 정보 조회",
        ],
      };
    }
  • Type definition (schema) for the ServerInfo output returned by the get_server_info handler.
    export interface ServerInfo {
      name: string;
      version: string;
      description: string;
      tools: string[];
    }
  • src/index.ts:244-272 (registration)
    Registration of the get_server_info tool in the MCP server. Includes empty input schema ({}), description, and thin wrapper handler that formats the output from getServerInfo() as MCP text content response.
    server.tool(
      "get_server_info",
      "이 MCP 서버의 정보와 사용 가능한 Tool 목록을 반환합니다.",
      {},
      async () => {
        const info = getServerInfo();
    
        const infoText = `
    === ${info.name} 서버 정보 ===
    
    버전: ${info.version}
    설명: ${info.description}
    
    사용 가능한 Tool:
    ${info.tools.map((t, i) => `${i + 1}. ${t}`).join("\n")}
    
    GitHub: https://github.com/dh1789/my-first-mcp
    `.trim();
    
        return {
          content: [
            {
              type: "text",
              text: infoText,
            },
          ],
        };
      }
    );
Behavior2/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. While it states the tool returns information (implying read-only), it doesn't clarify whether this requires authentication, has rate limits, what format the information comes in, or any other behavioral characteristics. For a tool with zero annotation coverage, this is insufficient disclosure.

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

Conciseness5/5

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

The description is extremely concise - a single Korean sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded with the core functionality and wastes no space on redundant information. Every word earns its place.

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 that this is a simple read-only tool with no parameters and no output schema, the description provides the basic purpose but lacks important context. Without annotations or output schema, the description should ideally specify what 'server information' includes and what format the 'available tool list' takes. The current description is minimally adequate but leaves gaps about the return format.

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 zero parameters (schema description coverage is 100%), so the baseline for a parameterless tool is 4. The description appropriately doesn't discuss parameters since none exist, and it focuses on what the tool returns rather than what it accepts as input.

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: '이 MCP 서버의 정보와 사용 가능한 Tool 목록을 반환합니다' (returns this MCP server's information and available tool list). It specifies both the verb ('반환합니다' - returns) and the resources (server info and tool list). However, it doesn't explicitly differentiate from siblings like 'server_status' 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. With siblings like 'server_status' that might provide similar server information, there's no indication of when this tool is appropriate versus other tools. The description simply states what it does without contextual usage information.

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/dh1789/my-first-mcp'

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