Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_route_list

List all BOS routes. Filter by module to discover specific API endpoints for ERP operations.

Instructions

List all BOS routes, optionally filtered by module

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleNo
limitNo

Implementation Reference

  • Handler function for boscli_route_list: calls client.get('/boscli/routes', args) to fetch routes from the API, optionally filtered by module and limit.
    handler: async (args, client) => client.get('/boscli/routes', args),
  • Schema definition for boscli_route_list: accepts optional 'module' (string) and 'limit' (number) parameters.
    schema: {
      module: { type: 'string', optional: true },
      limit: { type: 'number', optional: true },
    },
  • Tool registration as part of the routeTools array exported from src/tools/route.ts. The tool named 'boscli_route_list' is defined alongside 'boscli_route_by_module'.
    export const routeTools: McpTool[] = [
      {
        name: 'boscli_route_list',
        description: 'List all BOS routes, optionally filtered by module',
        schema: {
          module: { type: 'string', optional: true },
          limit: { type: 'number', optional: true },
        },
        handler: async (args, client) => client.get('/boscli/routes', args),
      },
      {
        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}`),
      },
    ];
Behavior2/5

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

No annotations provided, so description carries full burden. It implies a read-only operation but does not disclose behavior regarding limits, pagination, authentication, or any side effects. The 'limit' parameter is not explained.

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 very concise with a single sentence that is front-loaded. However, it could include more context without being overly verbose.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is insufficient. It does not explain what a 'route' is, the output format, or any limitations, making it inadequate for a complete understanding.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only clarifies the 'module' parameter for filtering. The 'limit' parameter is not mentioned at all, leaving its purpose ambiguous.

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 lists BOS routes and optionally filters by module. It distinguishes from the sibling 'boscli_route_by_module' by implying a broader scope ('list all' vs specific module). However, explicit differentiation is missing.

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 over alternatives like 'boscli_route_by_module'. The description only mentions optional filtering, no exclusions or context.

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