Skip to main content
Glama
bizino

BOS MCP Server

by bizino
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

bos_product_stock

Retrieve stock levels for a product across all locations by providing its product ID.

Instructions

Get stock levels for a product across all locations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idYes

Implementation Reference

  • src/tools/bos.ts:78-83 (handler)
    The handler for bos_product_stock. It makes a GET request to /mcp/products/{product_id}/stock via the BosApiClient.
    {
  name: 'bos_product_stock',
  description: 'Get stock levels for a product across all locations',
  schema: { product_id: { type: 'string' } },
  handler: async (args, client) => client.get(`/mcp/products/${args.product_id}/stock`),
},
  • src/tools/bos.ts:81-81 (schema)
    The input schema for bos_product_stock expects a single required string field: product_id.
    schema: { product_id: { type: 'string' } },
  • src/tools/bos.ts:78-83 (registration)
    The tool is registered as part of the productTools array (line 7) in src/tools/bos.ts, which is then spread into allTools in src/index.ts (line 33), src/http.ts (line 33), and src/stdio.ts (line 33). Tools are registered with the MCP SDK via server.tool() in each entry point.
    {
  name: 'bos_product_stock',
  description: 'Get stock levels for a product across all locations',
  schema: { product_id: { type: 'string' } },
  handler: async (args, client) => client.get(`/mcp/products/${args.product_id}/stock`),
},

Tool Definition Quality

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavior disclosure. It only states 'Get stock levels' without specifying whether the response includes per-location breakdowns, pending stock, or time sensitivity. This is insufficient for a tool with no annotation coverage.

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, front-loaded sentence with no extraneous words. It efficiently communicates the core function.

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?

Given the tool's simplicity (one required parameter, no output schema, no annotations), the description provides minimal but adequate context. However, it lacks details on return structure, error handling, and interpretation of 'stock levels,' making it only marginally complete.

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?

The input schema has one parameter (product_id) with no description. The tool description does not add any semantics beyond the parameter name, such as expected format, examples, or constraints. With 0% schema description coverage, the description should compensate but fails to do so.

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 the tool retrieves stock levels for a specific product across all locations. The verb 'Get' and resource 'stock levels for a product' are specific. It distinguishes from sibling tools like bos_inventory_list (which may be broader) and bos_inventory_low_stock (which focuses on low stock items).

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 implies usage when stock levels for a single product are needed but provides no explicit guidance on when to use this tool versus alternatives such as bos_inventory_list or bos_store_inventory. No when-not-to-use or prerequisite information is given.

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