Skip to main content
Glama

rr_get_inventory_health

Read-onlyIdempotent

Summarize store-wide inventory health by reporting stockout-risk counts at each level and active alert counts by type, so you can spot and prioritize replenishment issues.

Instructions

Store-wide inventory health summary: stockout-risk counts by level and active alert counts by type.

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": "rr_get_inventory_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds that the payload is aggregate counts rather than raw records, which is useful, but it does not say how 'level' or 'type' are enumerated, whether zero counts are included, or how fresh the data is.

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 front-loaded clause with zero filler, leading with the resource and following with the two metrics returned. Nothing could be removed without losing information.

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?

With no parameters, no nested objects, and no output schema, the burden is light, and the description tells the agent the shape of the summary it gets back. The only shortfall is that the value domains for 'level' and 'type' are unspecified, which mildly limits interpretation of the results.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline is 4. The schema has zero properties, meaning the call carries no arguments an agent could misuse.

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?

The sentence names a specific resource (store-wide inventory health) and specifies the two aggregates returned: stockout-risk counts by level and active alert counts by type. That is enough to distinguish it from per-item siblings like rr_get_inventory_position or rr_list_alerts, though it never names an alternative explicitly.

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 by the phrase 'store-wide ... summary' — an agent can infer this is the rollup view rather than a detail listing. There is no explicit statement of when to call it versus rr_get_store_health, rr_list_alerts, or rr_get_inventory_position, and no prerequisites or exclusions.

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