mcp-rona

Check RONA online availability for a SKU

rona_store_availability

Check if a RONA product SKU is available for online purchase. Reports inventory status for online buying only.

Instructions

Check whether a RONA SKU is available to buy online (inventory status). Note: real-time per-store stock levels and aisle/bay locations are not available from RONA's public APIs — this reports online purchasability only. Use rona_stores to find stores near a location.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sku": "<sku>"
    },
    "name": "rona_store_availability"
  }
}

Input Schema

Name	Required	Description	Default
`sku`	Yes	Product SKU / item number, e.g. '00277649'.
`lang`	No	Response language. Default 'en'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It clearly sets expectations by noting the tool only reports online availability and does not provide per-store data. However, it does not disclose return format, error behavior, or if any side effects exist (likely none). Still, it is transparent about its limited scope.

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?

Two sentences that front-load the main purpose, then add limitation and sibling reference. No superfluous text; every sentence adds value.

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?

Given the tool's simplicity (2 params, no nested objects) and no output schema, the description adequately explains its purpose and limitations. However, it omits what the return value looks like (e.g., a boolean or status string). Still, it is mostly complete for effective selection and invocation.

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%, so baseline is 3. The description adds no additional parameter meaning beyond the schema's built-in descriptions. It does reinforce the SKU example, but that is already present in schema.

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 verb 'Check' and the resource 'RONA SKU availability to buy online'. It distinguishes from siblings by specifying online purchasability only and referencing rona_stores for store-level data.

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?

Explicitly states limitations: real-time per-store stock levels are not available. Provides a sibling alternative (rona_stores) for finding stores, guiding the agent on when not to use this tool.

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

Deploy Server