Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_module_list

List all BOS modules with their enabled or disabled status to manage module availability.

Instructions

List all BOS modules with their enabled/disabled status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool 'boscli_module_list' is defined and exported in the moduleTools array along with other module tools. It is registered as an McpTool with name, description, schema (empty object), and handler.
    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'),
      },
  • The handler function that executes the tool logic: it makes a GET request to '/boscli/modules' using the BosApiClient client.
    {
      name: 'boscli_module_list',
      description: 'List all BOS modules with their enabled/disabled status',
      schema: {},
      handler: async (_, client) => client.get('/boscli/modules'),
  • The input schema is an empty object (no parameters required) for boscli_module_list.
    schema: {},
  • src/index.ts:55-76 (registration)
    The tool is registered with the MCP server via a loop that calls server.tool() with the tool's name, description, Zod schema, and a wrapper handler.
    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,
            };
          }
        }
      );
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden. The verb 'List' implies a read-only, non-destructive operation, and the output is clearly stated as enabled/disabled status. This is adequate transparency for a simple list tool with no 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 concise sentence with no wasted words. It is front-loaded with the action and key information.

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?

Given zero parameters and no output schema, the description completely covers the tool's purpose and return value. It adequately informs the agent what the tool does and what to expect.

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

Parameters5/5

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

The input schema has zero parameters, so schema coverage is complete. The description adds meaning by specifying the output: 'all BOS modules' and 'enabled/disabled status', going beyond the schema to clarify the tool's result.

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 ('List') and resource ('BOS modules') with a clear attribute ('enabled/disabled status'). It distinguishes itself from sibling tools like boscli_module_enable (which enables a module) and boscli_module_show (which likely shows details of a single module).

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?

The description implicitly suggests use for getting an overview of all modules and their status, but it does not explicitly state when to use this tool versus alternatives like boscli_module_show or boscli_health_modules. No exclusion criteria or context is provided.

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