Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_module_disable

Disable a BOS module by providing its name, deactivating it within the ERP system.

Instructions

Disable a BOS module by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_nameYesName of the module to disable

Implementation Reference

  • The handler definition for the boscli_module_disable tool. It accepts a 'module_name' argument and sends a POST request to /boscli/modules/{module_name}/disable via the BosApiClient.
    {
      name: 'boscli_module_disable',
      description: 'Disable a BOS module by name',
      schema: { module_name: { type: 'string', description: 'Name of the module to disable' } },
      handler: async (args, client) => client.post(`/boscli/modules/${args.module_name}/disable`),
    },
  • The schema definition for boscli_module_disable. It requires a single 'module_name' string parameter that specifies which module to disable.
    {
      name: 'boscli_module_disable',
      description: 'Disable a BOS module by name',
      schema: { module_name: { type: 'string', description: 'Name of the module to disable' } },
      handler: async (args, client) => client.post(`/boscli/modules/${args.module_name}/disable`),
    },
  • The moduleTools array containing the boscli_module_disable tool entry alongside other module-related tools. This array is exported and later imported in src/index.ts, src/stdio.ts, and src/http.ts where tools are registered with the MCP server via server.tool().
    export const moduleTools: McpTool[] = [
      {
        name: 'boscli_module_list',
        description: 'List all BOS modules with their enabled/disabled status',
        schema: {},
        handler: async (_, client) => client.get('/boscli/modules'),
      },
      {
        name: 'boscli_module_show',
        description: 'Get details of a specific BOS module',
        schema: { module_name: { type: 'string', description: 'Name of the module to check' } },
        handler: async (args, client) => client.get(`/boscli/modules/${args.module_name}`),
      },
      {
        name: 'boscli_module_enable',
        description: 'Enable a BOS module by name',
        schema: { module_name: { type: 'string', description: 'Name of the module to enable' } },
        handler: async (args, client) => client.post(`/boscli/modules/${args.module_name}/enable`),
      },
      {
        name: 'boscli_module_disable',
        description: 'Disable a BOS module by name',
        schema: { module_name: { type: 'string', description: 'Name of the module to disable' } },
        handler: async (args, client) => client.post(`/boscli/modules/${args.module_name}/disable`),
      },
    ];
  • src/tools/bos.ts:54-76 (registration)
    The registration loop in the main entry point (index.ts) that iterates over all tools (including moduleTools) and registers them with the MCP server using server.tool(). This is where boscli_module_disable gets registered with the MCP SDK.
      schema: {
        product_id: { type: 'string' },
        name: { type: 'string', optional: true },
        price: { type: 'number', optional: true },
        stock: { type: 'number', optional: true },
        status: { type: 'string', optional: true },
      },
      handler: async (args, client) => {
        const { product_id, ...data } = args;
        return client.put(`/mcp/products/${product_id}`, data);
      },
    },
    {
      name: 'bos_product_delete',
      description: 'Delete a product',
      schema: { product_id: { type: 'string' } },
      handler: async (args, client) => client.delete(`/mcp/products/${args.product_id}`),
    },
    {
      name: 'bos_product_variants',
      description: 'Get all variants for a product',
      schema: { product_id: { type: 'string' } },
      handler: async (args, client) => client.get(`/mcp/products/${args.product_id}/variants`),
  • The BosApiClient.post() method used by the boscli_module_disable handler to send the POST request to the backend API.
    async post<T>(path: string, data?: any): Promise<T> {
      return this.request<T>('POST', path, data);
    }
Behavior2/5

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

With no annotations, the description carries full burden but fails to disclose behavioral traits like whether disabling is reversible, impacts other modules, requires specific permissions, or affects system state. The single word 'disable' implies mutation but lacks detail.

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 with no unnecessary words, perfectly concise and front-loaded.

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 simplicity (one param, no output schema, no annotations), the description is minimally adequate but lacks context about the effect of disabling, how to re-enable, or error conditions. Slightly incomplete for operational clarity.

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 input schema already fully describes the 'module_name' parameter with 100% coverage. The description adds no extra meaning beyond the schema, meeting the baseline but not exceeding it.

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 'Disable a BOS module by name' clearly states the action (disable) and the resource (BOS module), with the method (by name). It effectively distinguishes from sibling tools like boscli_module_enable.

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 or why to use this tool, nor when to avoid it. It does not mention any context such as prerequisites, consequences of disabling a module, or alternatives (e.g., boscli_module_show to check status).

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