Skip to main content
Glama
bigl34

inFlow Inventory MCP Server

by bigl34

list_products

Search and retrieve products from inFlow Inventory using optional filters such as SKU, name, barcode, category, active status, or serial tracking. Include related data or counts to narrow results.

Instructions

Search and list products from inFlow Inventory with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuNoFilter by SKU
nameNoFilter by product name (partial match)
skipNoNumber of records to skip
sortNoProperty to sort by (e.g., name, sku, modifiedDate)
countNoNumber of records to return (max 100)
smartNoSmart search across multiple fields (name, description, SKU, barcode)
barcodeNoFilter by barcode
includeNoRelated data to include. Options: category, customFields, inventoryLines (serial numbers). Use filter trackSerials=true to get only serialized products.
isActiveNoFilter by active status
sortDescNoSort in descending order
categoryIdNoFilter by category ID
descriptionNoFilter by description
categoryNameNoFilter by category name (case-insensitive, resolves to categoryId)
includeCountNoInclude total record count in response
trackSerialsNoFilter to only return products that track serial numbers (serial numbers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0-alpha.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a read operation implicitly through 'search and list', but doesn't describe return format, pagination behavior, rate limits, or authentication requirements. For a tool with 15 parameters and no annotations, this is a significant gap.

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?

A single, efficient sentence that is front-loaded and wastes no words. It clearly states the core function without unnecessary elaboration.

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?

For a tool with 15 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain pagination (skip/count), sorting behavior, the smart search vs individual filters, or what 'include' does. The schema provides field-level descriptions, but the description should tie these together and explain overall behavior.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 15 parameters. The description adds no parameter-specific information beyond what's in the schema. Baseline 3 is correct when schema does the heavy lifting.

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?

Specifies the verb (search/list), resource (products), and source system (inFlow Inventory), which distinguishes it from get_product (single retrieval) and upsert_product (mutation). However, it doesn't explicitly differentiate itself from sibling list_* tools beyond the resources being different.

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 explicit guidance on when to use this tool versus alternatives like get_product or smart search. The description mentions 'optional filtering' but doesn't explain when to use which filter or why one would choose list vs search.

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