Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_store_inventory

Retrieve a summary of inventory for a specific store using its store ID to assess stock levels and availability.

Instructions

Get inventory summary for a specific store

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYes

Implementation Reference

  • The handler function that executes the 'bos_store_inventory' tool logic by making a GET request to the store inventory API endpoint.
    handler: async (args, client) => client.get(`/mcp/stores/${args.store_id}/inventory`),
  • Input schema for 'bos_store_inventory' - requires a 'store_id' string parameter.
    schema: { store_id: { type: 'string' } },
  • Registration of 'bos_store_inventory' as a tool in the storeTools array in bos.ts.
      name: 'bos_store_inventory',
      description: 'Get inventory summary for a specific store',
      schema: { store_id: { type: 'string' } },
      handler: async (args, client) => client.get(`/mcp/stores/${args.store_id}/inventory`),
    },
  • src/stdio.ts:40-41 (registration)
    Store tools (including bos_store_inventory) are spread into the allTools array for registration with the MCP server via stdio transport.
    ...storeTools,
    ...checkoutTools,
  • McpTool interface defining the structure that bos_store_inventory conforms to.
    export interface McpTool {
      name: string;
      description: string;
      schema: Record<string, any>;
      handler: (args: any, client: BosApiClient) => Promise<any>;
    }
Behavior2/5

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

No annotations provided, so the description must disclose behavior. It implies a read-only operation but does not explicitly state non-destructiveness, required permissions, or error handling for invalid store_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at six words, but it sacrifices necessary details. Front-loaded with purpose, but lacks structure for broader context.

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?

With one parameter, no annotations, and no output schema, the description provides minimal contextual completeness. It fails to explain what an inventory summary contains, typical use cases, or response format.

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 coverage is 0%, and the description adds no information about the store_id parameter beyond the schema's type (string). It does not explain format, example values, or how to obtain valid IDs.

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 the action ('Get') and resource ('inventory summary') with a scope ('for a specific store'). It distinguishes from sibling inventory tools like bos_inventory_list by implying aggregated data, but does not explicitly differentiate.

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 versus alternatives such as bos_inventory_list, bos_inventory_check, or bos_inventory_low_stock. Missing context for usage scenarios.

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