Skip to main content
Glama

Product Performance (ABC Analysis)

product_performance
Read-onlyIdempotent

Classify products by revenue using ABC analysis (top 80%, next 15%, bottom 5%) and review trends, margins, and daily sales velocity.

Instructions

Product performance report with ABC analysis. Category A = top 80% revenue, B = next 15%, C = bottom 5%. Includes trends, margins, and daily sales velocity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesUUID of a connected store (returned by store_connect with action="connect" or visible in store_connect with action="list" / the store_overview resource)
period_daysNoLook-back window for ABC classification, 7–90 days. Defaults to 30. Shorter windows favour recent trends; longer windows smooth seasonality.

Implementation Reference

  • `ProductPerformanceSchema` — Zod schema defining the shape of each product performance record (product_id, product_title, sku, units_sold, revenue, cost, profit, margin_percent, abc_category, revenue_share_percent, avg_daily_units, trend). Also exports the `ProductPerformance` type.
    export const ProductPerformanceSchema = z.object({
      product_id: z.string(),
      product_title: z.string(),
      sku: z.string().nullable(),
      units_sold: z.number().int(),
      revenue: z.number(),
      cost: z.number().nullable(),
      profit: z.number().nullable(),
      margin_percent: z.number().nullable(),
      abc_category: ABCCategorySchema,
      revenue_share_percent: z.number(),
      avg_daily_units: z.number(),
      trend: z.enum(['rising', 'stable', 'declining']),
    });
    export type ProductPerformance = z.infer<typeof ProductPerformanceSchema>;
Behavior3/5

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

Annotations already indicate read-only, non-destructive, and idempotent behavior. The description adds that it includes trends, margins, and velocity, which is helpful but does not disclose any behavioral nuances beyond the annotations.

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 two sentences with no redundancy. It front-loads the purpose and defines the ABC categories succinctly.

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?

While no output schema exists, the description covers key report components (trends, margins, velocity). It is sufficiently complete for a read-only report tool given the annotations and schema.

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 coverage is 100%, so baseline is 3. The description does not add meaning beyond what the schema provides for store_id and period_days; it only mentions high-level report contents.

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 tool generates a product performance report with ABC analysis, defining the revenue thresholds for categories A, B, and C. This distinguishes it from sibling tools like inventory_forecast or pricing_analyze.

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 usage for ABC analysis but does not explicitly state when to use this tool versus alternatives like report_daily or inventory_status. No exclusions or alternative suggestions are provided.

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/enzoemir1/shopops-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server