Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_route_by_module

Retrieve all routes for a specific BOS module. Filter routes by module name to view available endpoints.

Instructions

Get all routes for a specific BOS module

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleYesModule name to filter routes

Implementation Reference

  • Handler function that calls client.get('/boscli/routes/${args.module}') to fetch routes for a specific module. The module name from the args is interpolated into the URL path.
    {
      name: 'boscli_route_by_module',
      description: 'Get all routes for a specific BOS module',
      schema: { module: { type: 'string', description: 'Module name to filter routes' } },
      handler: async (args, client) => client.get(`/boscli/routes/${args.module}`),
  • Input schema for 'boscli_route_by_module' requiring a single string parameter 'module' with description 'Module name to filter routes'.
    schema: { module: { type: 'string', description: 'Module name to filter routes' } },
  • src/index.ts:54-76 (registration)
    Tool registration in src/index.ts: routeTools (including boscli_route_by_module) is registered via server.tool() in the allTools loop using toZodSchema() to convert the schema.
    // 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)
    Alternative registration in the stdio entry point (src/stdio.ts) - same loop-based registration of all tools including boscli_route_by_module.
    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)
    Alternative registration in the HTTP/SSE entry point (src/http.ts) - same loop-based registration of all tools including boscli_route_by_module.
    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 provided, and the description only states the basic function. It omits behavioral details such as expected behavior for missing modules, side effects, or required permissions. Since annotations are absent, the description should disclose more.

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 directly states the action. It is front-loaded with no extraneous words, but could potentially include more detail without losing conciseness.

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

Completeness4/5

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

For a simple tool with one parameter and no output schema, the description sufficiently explains the purpose. The parameter is self-explanatory given the schema, and the tool's simplicity means no further context is critical.

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%, with the parameter 'module' clearly described. The description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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?

Description clearly states 'Get all routes for a specific BOS module', with a specific verb and resource. It distinguishes from sibling tool 'boscli_route_list' which likely returns all routes, making purpose and differentiation clear.

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_route_list'. The context implies filtering by module, but lacks explicit when/when-not or alternative references.

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