Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_health_database

Check BOS database connectivity to diagnose and resolve connection issues with the ERP system.

Instructions

Check BOS database connectivity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for boscli_health_database tool. Makes a GET request to '/boscli/health/database' endpoint via the BosApiClient.
    name: 'boscli_health_database',
    description: 'Check BOS database connectivity',
    schema: {},
    handler: async (_, client) => client.get('/boscli/health/database'),
  • Empty schema/input validation for boscli_health_database (no parameters needed).
    schema: {},
  • The healthTools array is defined and exported from src/tools/health.ts, containing the boscli_health_database tool definition.
    export const healthTools: McpTool[] = [
      {
        name: 'boscli_health_check',
        description: 'Full BOS system health check - modules, database, cache, routes',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health'),
      },
      {
        name: 'boscli_health_modules',
        description: 'Check health of all BOS modules',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health/modules'),
      },
      {
        name: 'boscli_health_database',
        description: 'Check BOS database connectivity',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health/database'),
      },
      {
        name: 'boscli_health_cache',
        description: 'Check BOS cache systems',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health/cache'),
      },
      {
        name: 'boscli_health_schema',
        description: 'Check BOS database schema integrity',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health/schema'),
      },
    ];
  • src/index.ts:28-28 (registration)
    healthTools is spread into allTools in src/index.ts, registering all health tools including boscli_health_database.
    ...healthTools,
  • src/stdio.ts:27-46 (registration)
    healthTools is spread into allTools in src/stdio.ts for the STDIO transport server, registering boscli_health_database.
    const allTools: McpTool[] = [
      ...healthTools,
      ...moduleTools,
      ...routeTools,
      ...cacheTools,
      ...systemTools,
      ...productTools,
      ...orderTools,
      ...cartTools,
      ...customerTools,
      ...inventoryTools,
      ...voucherTools,
      ...loyaltyTools,
      ...storeTools,
      ...checkoutTools,
      ...promotionTools,
      ...engagementTools,
      ...erpTools,
      ...smartTools,
    ];
Behavior2/5

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

With no annotations, the description carries full burden, but it only states the action. It does not disclose whether the tool is read-only, requires authentication, or what the consequences of invocation are (e.g., does it simply ping or perform a full connection test?). This is insufficient for safe invocation.

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 sentence of four words, efficiently conveying the tool's purpose with no unnecessary content.

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?

The tool is simple (no parameters, no output schema), so the description is adequate for a basic understanding. However, it does not specify what the tool returns or how to interpret results, leaving some ambiguity for the 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 input schema has zero parameters with 100% coverage, so the description does not need to add parameter details. The baseline is 4, and no extra information is required.

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

Purpose5/5

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

The description clearly states the tool checks 'BOS database connectivity', using a specific verb and resource. It distinguishes from sibling tools like boscli_health_cache and boscli_health_modules, which focus on other components.

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 on when to use this tool vs. other health check tools, nor any alternatives or prerequisites mentioned. The agent is left to infer usage from the name alone.

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/bizino/bos-mcp'

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