Skip to main content
Glama
Sign In
Business Bridge MCP Server

Business Bridge MCP Server

by AiAgentKarl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

shopify_get_inventory

Retrieve inventory levels for all product variants from a Shopify store. Specify the connector name and optionally limit the number of products.

Instructions

Inventar-Levels aus einem Shopify-Store abrufen.

Zeigt Lagerbestände für alle Produkt-Varianten.

Args: connector_name: Name des Shopify-Connectors limit: Maximale Anzahl Produkte (Standard: 10, Max: 50)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "connector_name": "<connector_name>"
    },
    "name": "shopify_get_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
connector_nameYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the basic operation (retrieve) but does not mention authentication needs, rate limits, return format, or error handling.

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 extremely concise with two sentences plus parameter details. Every sentence adds value, and the main purpose is front-loaded.

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

Completeness4/5

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

For a simple two-parameter tool with no output schema, the description covers what the tool does and the parameters. It could mention the return format or error conditions, but is largely complete.

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

Parameters5/5

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

Schema description coverage is 0%, but the description provides useful meanings for both parameters: connector_name as the connector name and limit with default and max values, adding significant value beyond the schema.

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 it retrieves inventory levels from Shopify and shows stock for all product variants. It is distinct from sibling tools like shopify_get_orders and shopify_get_products.

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 use when inventory data is needed, but provides no explicit when-to-use guidance or comparisons to alternatives. It lacks exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools