Skip to main content
Glama
xuejike

Database Query MCP Server

by xuejike

query_mssql

Read-only

Execute read-only SQL queries on MSSQL databases to retrieve data securely. Connect using host, port, credentials, and database name to run SELECT statements.

Instructions

执行MSSQL数据库查询(只读模式)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYes数据库主机地址
portYes数据库端口
userYes数据库用户名
pwdYes数据库密码
dbYes数据库名称
querySqlYes要执行的SQL查询语句(仅支持SELECT等只读操作)

Implementation Reference

  • Handler function for the query_mssql tool. Performs read-only check and currently returns a 'not implemented' error as MSSQL support is stubbed out.
    async executeMSSQL(config) {
      const { querySql } = config;
      
      // 检查是否为只读查询
      if (!this.isReadOnlyQuery(querySql)) {
        return {
          success: false,
          error: "不允许执行非只读操作。仅支持SELECT、SHOW、DESCRIBE等查询语句。",
          code: "READONLY_VIOLATION"
        };
      }
      
      // MSSQL support needs to be implemented
      return {
        success: false,
        error: "MSSQL support needs to be implemented",
        code: "NOT_IMPLEMENTED"
      };
    }
  • Schema definition including input parameters, types, requirements, and annotations for the query_mssql tool.
    query_mssql: {
      name: "query_mssql",
      description: "执行MSSQL数据库查询(只读模式)",
      inputSchema: {
        type: "object",
        properties: {
          host: { 
            type: "string", 
            description: "数据库主机地址" 
          },
          port: { 
            type: "integer", 
            description: "数据库端口" 
          },
          user: { 
            type: "string", 
            description: "数据库用户名" 
          },
          pwd: { 
            type: "string", 
            description: "数据库密码" 
          },
          db: { 
            type: "string", 
            description: "数据库名称" 
          },
          querySql: { 
            type: "string", 
            description: "要执行的SQL查询语句(仅支持SELECT等只读操作)" 
          }
        },
        required: ["host", "port", "user", "pwd", "db", "querySql"]
      },
      annotations: {
        title: "MSSQL数据库查询工具(只读)",
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: false,
        openWorldHint: false
      }
    },
  • mcp-server.js:79-86 (registration)
    Registers query_mssql in the list of available tools returned by ListToolsRequest.
        tools: [
          config.tools.query_mysql,
          config.tools.query_postgresql,
          config.tools.query_mssql,
          config.tools.query_oracle
        ]
      };
    });
  • mcp-server.js:44-46 (registration)
    Registers the dispatch to query_mssql handler in the CallToolRequest switch statement.
    case config.tools.query_mssql.name:
      result = await dbTool.executeMSSQL(request.params.arguments);
      break;
  • Helper function to check if SQL query is read-only, used by all database query handlers including MSSQL.
    isReadOnlyQuery(sql) {
      // 转换为小写以便比较
      const lowerSql = sql.trim().toLowerCase();
      
      // 允许的只读操作关键词
      const allowedPatterns = [
        /^select/,
        /^show/,
        /^describe/,
        /^desc/,
        /^explain/,
        /^use/
      ];
      
      // 禁止的写操作关键词
      const forbiddenPatterns = [
        /insert/,
        /update/,
        /delete/,
        /drop/,
        /truncate/,
        /alter/,
        /create/,
        /replace/,
        /grant/,
        /revoke/,
        /commit/,
        /rollback/,
        /savepoint/,
        /set/
      ];
      
      // 检查是否包含禁止的关键词
      for (const pattern of forbiddenPatterns) {
        if (pattern.test(lowerSql)) {
          return false;
        }
      }
      
      // 检查是否以允许的关键词开头
      for (const pattern of allowedPatterns) {
        if (pattern.test(lowerSql)) {
          return true;
        }
      }
      
      // 如果既不明确允许也不明确禁止,默认为不安全
      return false;
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and idempotentHint=false. The description adds the read-only mode context ('只读模式'), which reinforces but doesn't significantly expand beyond annotations. It doesn't disclose additional behavioral traits like rate limits, authentication needs beyond parameters, or error handling.

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, efficient sentence in Chinese that directly states the tool's purpose and key constraint ('只读模式'). It's front-loaded with no unnecessary words, 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.

Completeness3/5

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

Given the tool's complexity (database querying with 6 required parameters), annotations cover safety aspects (read-only, non-destructive), but there's no output schema. The description is minimal and doesn't explain return values, error cases, or connection behavior. It's adequate but lacks depth for a tool with significant operational context.

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?

Schema description coverage is 100%, with all parameters well-documented in the input schema. The description doesn't add meaningful parameter semantics beyond what's already in the schema, such as format examples or constraints. Baseline 3 is appropriate since the schema carries the full burden.

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 ('执行MSSQL数据库查询') and resource ('MSSQL数据库'), specifying it's for read-only operations. It distinguishes from siblings by mentioning MSSQL specifically, though it doesn't explicitly contrast with other database query tools like query_mysql or query_oracle.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for MSSQL database queries in read-only mode, but doesn't provide explicit guidance on when to use this tool versus alternatives like query_mysql or query_oracle. No exclusions or prerequisites are mentioned beyond the read-only constraint.

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/xuejike/coding-db-mcp'

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