Skip to main content
Glama

get_restock_alerts

Retrieve aggregated public restock alerts for single-board computers and mini PCs to track when hardware becomes available again.

Instructions

Get aggregated public restock signals.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/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 behavioral burden. It does hint that results are "aggregated" (pre-summarized rather than raw events) and "public" (no private scope), which is mild value, but it says nothing about auth needs, rate limits, freshness, pagination, or result ordering.

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

Conciseness3/5

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

A single short sentence with the resource front-loaded and no filler, so it is efficient. However, the brevity comes from omission rather than discipline; the sentence is under-specified rather than tight.

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

Completeness2/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 need not be described, but the description still fails to convey what "aggregated restock signals" actually contains or how the "public" qualifier limits the data. For a fetch tool with a pagination-style parameter, this is too thin to call correctly with confidence.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter "limit" (default 20), so the description needed to compensate and does not. It never says what limit bounds — number of signals, stores, or days — nor whether a maximum exists, leaving the one knob an agent must set unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description supplies a verb ("Get") and a resource phrase ("aggregated public restock signals"), which is more than a tautology, but "signals" and "restock" are never grounded — no product domain, no source, no unit of aggregation. It also gives no differentiation from the sibling tools it sits beside (boards, deals, breakeven, etc.), so an agent must guess at scope.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of alternatives, and no stated prerequisites. The word "public" implies no authenticated/private data is returned, but the description never says when an agent should prefer this over other read tools or what situation it answers.

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