Skip to main content
Glama
NakiriYuuzu

MSSQL MCP Server

by NakiriYuuzu

connection-status

Verify the current database connection status on MSSQL MCP Server to ensure stable and reliable interactions with Microsoft SQL Server databases.

Instructions

檢查目前的資料庫連接狀態

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that implements the logic for the 'connection-status' tool: checks connection status, current database, tests the connection, and returns a text response with the status.
    async () => {
      try {
        const isConnected = mssqlManager.isConnected()
        const currentDb = mssqlManager.getCurrentDatabase()
    
        if (!isConnected) {
          return {
            content: [
              {
                type: 'text' as const,
                text: '狀態: 未連接到資料庫伺服器'
              }
            ]
          }
        }
    
        const testResult = await mssqlManager.testConnection()
        const status = testResult ? '已連接且運作正常' : '連接異常'
    
        return {
          content: [
            {
              type: 'text' as const,
              text: `狀態: ${status}${currentDb ? `\n目前資料庫: ${currentDb}` : '\n未選擇資料庫'}`
            }
          ]
        }
      } catch (error) {
        return {
          content: [
            {
              type: 'text' as const,
              text: `檢查連接狀態失敗: ${error instanceof Error ? error.message : String(error)}`
            }
          ]
        }
      }
    }
  • src/index.ts:432-475 (registration)
    Registers the 'connection-status' tool with the MCP server, providing title, description, and the inline handler function.
      'connection-status',
      {
        title: '連接狀態',
        description: '檢查目前的資料庫連接狀態'
      },
      async () => {
        try {
          const isConnected = mssqlManager.isConnected()
          const currentDb = mssqlManager.getCurrentDatabase()
    
          if (!isConnected) {
            return {
              content: [
                {
                  type: 'text' as const,
                  text: '狀態: 未連接到資料庫伺服器'
                }
              ]
            }
          }
    
          const testResult = await mssqlManager.testConnection()
          const status = testResult ? '已連接且運作正常' : '連接異常'
    
          return {
            content: [
              {
                type: 'text' as const,
                text: `狀態: ${status}${currentDb ? `\n目前資料庫: ${currentDb}` : '\n未選擇資料庫'}`
              }
            ]
          }
        } catch (error) {
          return {
            content: [
              {
                type: 'text' as const,
                text: `檢查連接狀態失敗: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          }
        }
      }
    )
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 checks connection status, implying a read-only operation, but doesn't specify what information is returned (e.g., success/failure, latency, error details), whether it requires authentication, or if it has side effects. This leaves significant gaps in understanding the tool's behavior.

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 a single, clear sentence in Chinese that directly states the tool's purpose without any unnecessary words or structural fluff. It is front-loaded and efficiently communicates the core function, making it highly concise and well-structured.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but adequate for basic understanding. However, it lacks details on what the check entails (e.g., returns a boolean, detailed status, or error), making it incomplete for an agent to fully anticipate the tool's behavior without additional context.

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, meaning no parameters are documented. The description doesn't mention any parameters, which is appropriate since none exist. It earns a baseline 4 because it doesn't need to compensate for missing parameter info, but loses a point for not explicitly noting the lack of inputs.

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 action ('檢查' meaning 'check' or 'inspect') and the target ('資料庫連接狀態' meaning 'database connection status'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'connect-database' or 'disconnect', which also relate to connection management, so it doesn't reach the highest clarity level.

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 prerequisites (e.g., whether a connection must be established first), exclusions, or comparisons to siblings like 'connect-database' for establishing connections or 'disconnect' for terminating them, leaving the agent with minimal context for selection.

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

Related 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/NakiriYuuzu/Mssql-Mcp'

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