Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dollartree_stock_status

Get Dollar Tree stock status for one SKU. Returns the current stock status and orderable, in-stock, backorderable, and preorderable quantities for one product SKU.

Instructions

Get Dollar Tree stock status for one SKU. Returns the current stock status and orderable, in-stock, backorderable, and preorderable quantities for one product SKU. Use the product id and child SKU repository id returned by the Dollar Tree product endpoints.

Input Schema

NameRequiredDescriptionDefault
sku_idYesSKU repository id from the product's childSKUs
product_idYesDollar Tree product id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned stock fields and single-SKU scope, but it does not describe error behavior, permissions, rate limits, or explicitly confirm that the operation is read-only.

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?

The definition is three concise sentences, front-loaded with the core action and return values, followed by the required parameter source. No sentence is wasted.

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?

For a low-complexity, two-parameter read tool with a fully described schema and no output schema, the description is largely complete: it explains the inputs' source and the returned stock fields. Minor gaps remain around error behavior and whether stock is online-only versus store-specific.

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 schema already documents both parameters. The description adds useful sourcing context by telling the agent to obtain the product id and child SKU repository id from the Dollar Tree product endpoints.

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 states a specific verb and resource (get Dollar Tree stock status for one SKU) and enumerates the returned stock fields. It distinguishes this lookup from price or product-detail siblings without needing to inspect the schema.

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

Usage Guidelines4/5

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

It gives clear prerequisite guidance: use the product id and child SKU repository id returned by the Dollar Tree product endpoints. It does not explicitly name alternatives or exclusions, but the context for use is clear.

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