Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_accounting_summary

Retrieve a summary of sales, purchases, expenses, and journal entries to quickly assess financial performance.

Instructions

Get sales, purchases, expenses, and journal entry summary

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool definition for 'bos_accounting_summary' with an empty schema and a handler that calls client.get('/mcp/erp/accounting/summary').
    name: 'bos_accounting_summary',
    description: 'Get sales, purchases, expenses, and journal entry summary',
    schema: {},
    handler: async (_, client) => client.get('/mcp/erp/accounting/summary'),
  • The schema for 'bos_accounting_summary' is an empty object (no input parameters required).
    {
      name: 'bos_accounting_summary',
      description: 'Get sales, purchases, expenses, and journal entry summary',
      schema: {},
      handler: async (_, client) => client.get('/mcp/erp/accounting/summary'),
    },
  • src/index.ts:44-44 (registration)
    The erpTools array (which contains bos_accounting_summary) is spread into allTools for registration.
    ...erpTools,
  • src/index.ts:55-76 (registration)
    The registration loop that iterates over all tools (including bos_accounting_summary) and registers them with the McpServer 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,
            };
          }
        }
      );
    }
  • The BosApiClient.get() method used by the handler to call GET /mcp/erp/accounting/summary on the backend API.
    async get<T>(path: string, params?: Record<string, any>): Promise<T> {
      return this.request<T>('GET', path, undefined, params);
    }
Behavior1/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It does not mention any side effects, authentication needs, rate limits, or that it is a read-only operation.

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 sentence that conveys the essential purpose without extraneous words. It is perfectly concise and front-loaded.

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?

The description lists the categories covered but does not specify the output format (e.g., totals, counts, time periods) or provide any structure. Given the absence of an output schema, more detail would be beneficial for an agent to understand what 'summary' entails.

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?

The tool has zero parameters and the schema coverage is 100%. Since no parameters exist, the description adds no additional meaning, but the baseline for 0 parameters is 4.

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 retrieves a summary of sales, purchases, expenses, and journal entries. The verb 'Get' and specific resource are well-defined, but it does not explicitly distinguish itself from sibling tools like bos_expense_list or bos_purchase_list, which provide detailed lists.

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 given on when to use this tool versus the detailed list tools (e.g., bos_expense_list). The description does not indicate scenarios where a summary is preferable.

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