Skip to main content
Glama

List products

list_products
Read-only

List the business's products with price, cost, stock and sales totals. These are catalogue items for sale; for recorded money-out use list_expenses and money-in use list_income. Archived products are included and carry archived: true; archiving hides nothing server-side.

Input Schema

NameRequiredDescriptionDefault
toNoOnly rows on/before this date (ISO 8601). Rows without a date are kept.
maxNoOnly rows whose amount is at most this (inclusive). Rows with no amount are excluded when min/max is set.
minNoOnly rows whose amount is at least this (inclusive). Rows with no amount are excluded when min/max is set. Applied before pagination.
fromNoOnly rows on/after this date (ISO 8601, e.g. "2026-01-01"). Rows without a date are kept.
limitNoMax rows to return in this page (default 50). Responses include next_cursor / truncated / total; pass next_cursor back as `cursor` to fetch the next page. Never silently truncated.
queryNoCase-insensitive substring filter — keeps only rows whose text (name, notes, and other string fields) contains this. Applied before pagination, so total/next_cursor reflect the filtered set.
cursorNoOpaque pagination cursor. Omit for the first page; pass the next_cursor from a previous response verbatim to fetch the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real behavioral context beyond that: archived products are included, they carry archived: true, and archiving hides nothing server-side — a fact an agent could not infer from the schema. It does not restate pagination behavior, but the schema's limit/cursor descriptions already carry that.

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?

Three tight sentences, front-loaded with what the tool returns before the disambiguation and the archived caveat. Minor redundancy between 'Archived products are included' and 'archiving hides nothing server-side', but the repetition reinforces rather than pads.

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

Completeness5/5

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

No output schema exists, so the description carries the return burden — and it does by naming the returned fields and the archived flag. Combined with fully documented parameters and a readOnly annotation, an agent has everything needed to call it correctly.

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% and every parameter (from/to, min/max, query, limit, cursor) is fully documented in the schema. The description adds no extra parameter meaning — notably it never explains why a product listing accepts date and amount filters, which is the one place it could have compensated.

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?

States a specific verb and resource (list the business's products) and immediately characterizes the rows as catalogue items for sale, while naming the returned fields (price, cost, stock, sales totals). This separates it cleanly from list_expenses, list_income, and list_assets without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names two concrete alternatives with the condition that selects them: money-out goes to list_expenses and money-in to list_income. That is an explicit when-not routing rule for the most likely confusion, not an implied one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources