Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_system_info

Get BOS system information including version, PHP, Laravel, and environment details.

Instructions

Get BOS system information - version, PHP, Laravel, environment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for boscli_system_info - makes a GET request to /boscli/system/info endpoint via BosApiClient
    {
      name: 'boscli_system_info',
      description: 'Get BOS system information - version, PHP, Laravel, environment',
      schema: {},
      handler: async (_, client) => client.get('/boscli/system/info'),
    },
  • Empty schema (no input parameters) for boscli_system_info
    schema: {},
    handler: async (_, client) => client.get('/boscli/system/info'),
  • src/index.ts:54-76 (registration)
    Registration loop in index.ts - all tools (including boscli_system_info) are registered with the MCP server via server.tool()
    // 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/http.ts:55-77 (registration)
    Registration loop in HTTP server (src/http.ts) - all tools including boscli_system_info registered with the MCP server 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,
              };
            }
          }
        );
      }
      return server;
    }
  • BosApiClient.get() helper - the method called by the boscli_system_info handler to perform the GET request
    async get<T>(path: string, params?: Record<string, any>): Promise<T> {
      return this.request<T>('GET', path, undefined, params);
    }
Behavior3/5

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

The verb 'Get' implies read-only, but without annotations, the description does not disclose potential behavioral traits like authentication needs or rate limits. It adds minimal behavioral context beyond the purpose.

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?

Single, concise sentence that front-loads the key action and items. Every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema tool, the description covers what the tool returns (version, PHP, Laravel, environment), making it complete for its complexity.

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?

No parameters exist, so no additional parameter info is needed. The description adds no param semantics, but baseline for 0 params with high schema coverage is 3; however, the lack of parameters makes the description sufficient.

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 'Get BOS system information' and lists specific items (version, PHP, Laravel, environment), distinguishing it from sibling tools like boscli_system_deploy_status or boscli_system_git_status.

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 when/when-not or alternatives provided. For a simple retrieval tool, usage is implied but guidance could be clearer given many sibling system tools.

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