Skip to main content
Glama
bigl34

inFlow Inventory MCP Server

by bigl34
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_vendors

Retrieve and filter vendor records by name, email, or active status, with sorting, pagination, and optional related data included.

Instructions

Search and list vendors with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by vendor name (partial match)
skipNoNumber of records to skip
sortNoProperty to sort by (e.g., name, modifiedDate)
countNoNumber of records to return (max 100)
emailNoFilter by email
includeNoRelated data to include (e.g., contacts, paymentTerms)
isActiveNoFilter by active status
sortDescNoSort in descending order
includeCountNoInclude total record count in response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0-alpha.2

TDQS

B3.2/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. It notes only that filtering is optional (implying an unfiltered call returns all vendors) but says nothing about pagination defaults, result caps, ordering behavior, or permissions for what is a 9-parameter list operation.

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

Conciseness4/5

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

A single seven-word sentence with no filler and the core action front-loaded. It is efficient, though arguably under-specified rather than deliberately tight.

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?

With 9 optional parameters at 100% schema coverage and no output schema, the description is barely adequate. It omits pagination/default behavior and how results are returned, which an agent calling a list endpoint would benefit from knowing.

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 all nine parameters are already documented in the schema (partial match, max 100, sort fields, include options). The description adds no syntax, format, or default details beyond that, so the baseline 3 applies.

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?

States a clear verb+resource ('Search and list vendors') that distinguishes it from the mutation siblings upsert_vendor/set_vendor and the single-record get_vendor. However, it never explicitly names those alternatives, so the differentiation is only implicit.

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?

'with optional filtering' implies the tool is for filtered browsing, but there is no explicit when-to-use, when-not-to-use, or pointer to get_vendor for a single vendor. Usage is left to inference.

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