Skip to main content
Glama
Sign In
bluebonnet-sales

bluebonnet-sales

by hostedinthebarn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

low_stock

Read-only

Identifies products with stock at or below a threshold and lists them lowest-first so you can prioritize replenishment.

Instructions

Products with stock at or below a threshold, lowest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "low_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
thresholdNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the useful ordering trait ('lowest first') but omits whether zero or negative stock is included, which catalog it reads, and how many rows come back.

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?

One short sentence with the filter and the sort order front-loaded; nothing is wasted or padded.

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?

An output schema exists, so return shape needn't be explained, but for a reporting tool the description should still note scope limits (which products, whether inactive/discontinued items appear, result cap). Those gaps leave the agent guessing at what a call actually returns.

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 0%, so the description carries the burden for the single parameter. It does clarify the comparison is inclusive ('at or below'), but never states units, valid range, or that the default is 10 — the agent must open the schema to learn the default.

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 concrete resource ('Products') with a specific filter ('stock at or below a threshold') and an ordering rule ('lowest first'). It does not differentiate from siblings like run_query, which could produce the same result, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is a convenience report for restocking, but nothing says when to prefer it over run_query or how it relates to sales_summary. No exclusions or prerequisites are given.

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