Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_module_enable

Activate a specific BOS module by name to enable its functionality within the ERP system.

Instructions

Enable a BOS module by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_nameYesName of the module to enable

Implementation Reference

  • The handler for 'boscli_module_enable' - sends a POST request to /boscli/modules/{module_name}/enable via the BosApiClient.
    {
      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`),
  • Schema definition for boscli_module_enable: requires a 'module_name' string field.
    schema: { module_name: { type: 'string', description: 'Name of the module to enable' } },
  • src/index.ts:55-76 (registration)
    Registration in src/index.ts: the tool is registered via server.tool() with its name, description, Zod schema, and handler wrapped in a try-catch.
    for (const tool of allTools) {
      const zodSchema = toZodSchema(tool.schema);
    
      server.tool(
        tool.name,
        tool.description,
        zodSchema.shape,
        async (args: any) => {
          try {
            const result = await tool.handler(args, client);
            return {
              content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (error: any) {
            return {
              content: [{ type: 'text' as const, text: JSON.stringify({ error: error.message || 'Unknown error' }) }],
              isError: true,
            };
          }
        }
      );
    }
  • src/stdio.ts:54-75 (registration)
    Registration in src/stdio.ts: same pattern - tool registered with MCP SDK via server.tool().
    for (const tool of allTools) {
      const zodSchema = toZodSchema(tool.schema);
      server.tool(
        tool.name,
        tool.description,
        zodSchema.shape,
        async (args: any) => {
          try {
            const result = await tool.handler(args, client);
            return {
              content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (error: any) {
            return {
              content: [{ type: 'text' as const, text: JSON.stringify({ error: error.message || 'Unknown error' }) }],
              isError: true,
            };
          }
        }
      );
    }
  • src/http.ts:55-75 (registration)
    Registration in src/http.ts: same pattern - tool registered with MCP SDK via server.tool().
    for (const tool of allTools) {
      const zodSchema = toZodSchema(tool.schema);
      server.tool(
        tool.name,
        tool.description,
        zodSchema.shape,
        async (args: any) => {
          try {
            const result = await tool.handler(args, client);
            return {
              content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (error: any) {
            return {
              content: [{ type: 'text' as const, text: JSON.stringify({ error: error.message || 'Unknown error' }) }],
              isError: true,
            };
          }
        }
      );
    }
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. It only states the action without disclosing effects (e.g., what happens if module already enabled, required permissions, reversibility). For a mutation tool, this is insufficient.

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

Conciseness4/5

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

The description is a single concise sentence that clearly communicates the tool's function. It is front-loaded and efficient, though it could benefit from slightly more context without becoming verbose.

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?

For a tool that modifies system state, the description lacks information on side effects, prerequisites, and constraints. No output schema or behavioral details are provided, making it incomplete despite the tool's simplicity.

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 coverage is 100% with module_name described as 'Name of the module to enable'. The description adds no extra meaning beyond the schema; baseline score is appropriate.

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 uses a specific verb ('Enable') and resource ('a BOS module'), clearly stating the action. Among siblings like boscli_module_disable, boscli_module_list, and boscli_module_show, this tool is well-differentiated by its enablement focus.

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?

No explicit guidance on when to use this tool versus alternatives like boscli_module_disable or boscli_module_list. The usage is implied from the action (enable), but without context on prerequisites or conditions, the agent must infer.

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