Crawlora MCP

dollartree_stock_status

Read-only

Get current Dollar Tree stock status and in-stock, orderable, backorderable, and preorderable quantities for one product SKU. Pass product_id from dollartree_search and the matching sku_id from that product's childSKUs in dollartree_product; use dollartree_price for price values. An unknown product returns not found; a response with mismatched SKU identity is rejected.

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": {
      "product_id": "<product_id>",
      "sku_id": "<sku_id>"
    },
    "name": "dollartree_stock_status"
  }
}

Input Schema

Name	Required	Description	Default
`sku_id`	Yes	Required. SKU repository id from the selected product's childSKUs.
`product_id`	Yes	Required. Dollar Tree product repository id returned by dollartree_search.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuine error-path behavior beyond them: an unknown product returns not found, and a response with mismatched SKU identity is rejected. What's missing is any mention of rate limits, caching, or freshness of stock data — relevant for an availability check whose values change over time.

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

Conciseness4/5

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

Three sentences, all load-bearing: capability, then id provenance plus the price alternative, then failure modes. Slightly dense, but the core purpose is front-loaded and nothing is redundant.

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 an output schema present, the description needn't enumerate return fields, and it covers inputs, provenance, alternatives, and error cases. The only gap for a live-inventory lookup is absence of any note on data freshness or caching.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic value by explaining where each id originates and that both must be consistent with the same product. That provenance and the identity-mismatch consequence are not in the 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?

States a specific verb and resource ('Get current Dollar Tree stock status') plus exactly what fields are returned: in-stock, orderable, backorderable, preorderable quantities for one SKU. It also distinguishes itself from dollartree_price and implicitly from search/product, so an agent can pick it without opening sibling schemas.

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?

Gives an explicit prerequisite chain: product_id comes from dollartree_search, sku_id from that product's childSKUs in dollartree_product, and price values belong to dollartree_price instead. That is concrete when-to-use and when-to-use-something-else guidance, not implied usage.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?