Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_system_logs

Retrieve recent BOS ERP log entries filtered by severity level and line count for system monitoring and troubleshooting.

Instructions

Read recent BOS log entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNo
levelNo

Implementation Reference

  • The handler for 'boscli_system_logs' tool. It calls client.get('/boscli/system/logs', args) to fetch recent BOS log entries from the API, passing optional query parameters (lines, level).
    name: 'boscli_system_logs',
    description: 'Read recent BOS log entries',
    schema: {
      lines: { type: 'number', optional: true },
      level: { type: 'string', enum: ['error', 'warning', 'info'], optional: true },
    },
    handler: async (args, client) => client.get('/boscli/system/logs', args),
  • Input schema for 'boscli_system_logs': optional 'lines' (number) and optional 'level' (enum: error, warning, info). Validated via toZodSchema() at registration time.
    schema: {
      lines: { type: 'number', optional: true },
      level: { type: 'string', enum: ['error', 'warning', 'info'], optional: true },
    },
  • src/index.ts:54-76 (registration)
    Registration in src/index.ts: all tools (including boscli_system_logs via systemTools spread) are iterated and registered via server.tool() with Zod schema conversion and error-handled handler wrapper.
    // Register all tools with proper Zod schemas
    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-74 (registration)
    Registration in src/stdio.ts (STDIO transport): same pattern as index.ts — systemTools spread into allTools, then each tool registered 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 (HTTP/SSE transport): same pattern — systemTools spread into allTools, each tool registered 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?

With no annotations, the description only indicates a read operation but does not disclose what 'recent' means, any limitations, or side effects.

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, front-loaded sentence with no wasted words. It is appropriately concise for the tool's simplicity.

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 low complexity (2 optional params, no output schema), the description is partially complete. It conveys the core function but lacks details on filtering and recency, leaving some gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description does not mention the parameters (lines, level) at all, failing to add meaning beyond the input schema.

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 it reads recent BOS log entries, using a specific verb and resource. However, it does not differentiate from sibling tools like boscli_health_*, but the resource 'log entries' is distinct enough.

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 is provided on when to use this tool vs alternatives, nor any context for the optional parameters like lines or level.

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