Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_order_shipping_info

Retrieve shipping information for an order by order ID. Includes tracking status and carrier details.

Instructions

Get shipping information for an order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes

Implementation Reference

  • The handler for bos_order_shipping_info. It calls client.get() with the path /mcp/orders/{order_id}/shipping to fetch shipping information for a given order.
    handler: async (args, client) => client.get(`/mcp/orders/${args.order_id}/shipping`),
  • The schema for bos_order_shipping_info: accepts a required order_id string.
    schema: { order_id: { type: 'string' } },
  • The full tool definition entry for bos_order_shipping_info, registered as part of the orderTools array.
      name: 'bos_order_shipping_info',
      description: 'Get shipping information for an order',
      schema: { order_id: { type: 'string' } },
      handler: async (args, client) => client.get(`/mcp/orders/${args.order_id}/shipping`),
    },
  • The BosApiClient.get() method that the handler delegates to, making a GET request to the specified path with optional query params.
    async get<T>(path: string, params?: Record<string, any>): Promise<T> {
      return this.request<T>('GET', path, undefined, params);
    }
  • src/index.ts:55-76 (registration)
    All tools (including bos_order_shipping_info via orderTools spread) are registered on the MCP server with Zod schema conversion and error handling.
    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 are provided, and the description only states a read operation ('Get'). It does not disclose any behavioral traits like idempotency, authentication requirements, or side effects. The description fails to add value beyond the obvious.

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 brief (6 words) but lacks structure. It does not front-load key information or provide any contextual sentences. While concise, it sacrifices completeness.

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 single parameter and no output schema, the description adequately identifies the tool's purpose. However, it fails to specify what shipping information is returned (e.g., address, carrier, tracking) or any limitations (e.g., only for completed orders).

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the one parameter (order_id) beyond its type. No additional meaning or format guidance is provided, which is insufficient given the lack of schema comments.

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?

The description clearly states the action ('Get') and the resource ('shipping information for an order'), distinguishing it from sibling tools like bos_order_show (full order details) and bos_order_update_shipping (modify shipping).

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?

The description provides no guidance on when to use this tool versus alternatives, such as bos_order_show or bos_delivery_shipment_list. No when/ when-not context 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