Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_module_show

Get detailed information about a specific module in the BOS ERP system. Provide the module name to retrieve its configuration, status, and metadata for troubleshooting and management.

Instructions

Get details of a specific BOS module

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_nameYesName of the module to check

Implementation Reference

  • The handler for 'boscli_module_show'. It accepts a 'module_name' parameter and makes a GET request to /boscli/modules/{module_name} via the BosApiClient.
    {
      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}`),
  • The input schema for 'boscli_module_show' declares a required 'module_name' string parameter.
    schema: { module_name: { type: 'string', description: 'Name of the module to check' } },
  • src/index.ts:55-76 (registration)
    The tool registration loop in src/index.ts iterates over allTools (including moduleTools) and calls server.tool() to register each one with MCP.
    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/index.ts:29-30 (registration)
    moduleTools is imported and spread into the allTools array in src/index.ts, which is how the tool gets registered.
    ...moduleTools,
    ...routeTools,
  • The McpTool interface defines the shape (name, description, schema, handler) that the tool definition conforms to.
    export interface McpTool {
      name: string;
      description: string;
      schema: Record<string, any>;
      handler: (args: any, client: BosApiClient) => Promise<any>;
    }
    
    export interface ToolCategory {
      name: string;
      tools: McpTool[];
    }
    
    /**
     * Convert our simple schema format to Zod schema for MCP SDK.
     * Input: { field: { type: 'string', optional: true, description: '...' } }
     * Output: z.object({ field: z.string().optional().describe('...') })
     */
    export function toZodSchema(schema: Record<string, any>): z.ZodObject<any> {
      const shape: Record<string, z.ZodTypeAny> = {};
    
      for (const [key, def] of Object.entries(schema)) {
        let field: z.ZodTypeAny;
    
        switch (def.type) {
          case 'number':
            field = z.number();
            break;
          case 'boolean':
            field = z.boolean();
            break;
          case 'array':
            field = z.array(z.any());
            break;
          case 'object':
            field = z.record(z.any());
            break;
          case 'string':
          default:
            if (def.enum) {
              field = z.enum(def.enum);
            } else {
              field = z.string();
            }
            break;
        }
    
        if (def.description) {
          field = field.describe(def.description);
        }
    
        if (def.optional) {
          field = field.optional();
        }
    
        shape[key] = field;
      }
    
      return z.object(shape);
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not disclose that this is a read-only operation, what 'details' includes, permissions required, or any side effects. The minimal statement lacks behavioral context.

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 concise sentence with no unnecessary words. It is appropriately short for a simple tool.

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 required param, no output schema), the description provides minimal but adequate information to understand the basic purpose. However, it lacks details about what 'details' entails, error handling, or typical usage scenarios. Completeness is borderline acceptable.

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% (one param with description). The description adds no extra meaning beyond the schema; it only says 'Name of the module to check'. Baseline 3 is appropriate as schema does the heavy lifting.

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 'Get details of a specific BOS module' uses a specific verb ('get details') and identifies the resource ('a specific BOS module'). It clearly distinguishes from sibling tools like boscli_module_list (list all) and boscli_module_disable (disable).

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. alternatives like boscli_module_list or other module-related tools. The description does not specify context, prerequisites, or exclusions.

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