Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dollartree_price

Get Dollar Tree product prices. Returns the current list price and per-SKU prices from Dollar Tree's public pricing resource for one product repository id, including the upstream price-range flag.

Instructions

Get Dollar Tree product prices. Returns the current list price and per-SKU prices from Dollar Tree's public pricing resource for one product repository id, including the upstream price-range flag.

Input Schema

NameRequiredDescriptionDefault
product_idYesDollar Tree product id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.5/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 burden, and it does disclose the return payload (current list price, per-SKU prices, upstream price-range flag) plus the upstream source. It says nothing about read-only behavior, caching/freshness of prices, rate limits, or whether per-SKU pricing corresponds to variants or store regions.

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?

Two sentences, front-loaded with the action and resource, with the return contents following immediately. Minor waste in the vendor boilerplate phrase 'Dollar Tree's public pricing resource,' but nothing is padded.

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?

There is no output schema, and the description compensates by enumerating the returned fields, which is the key missing piece for a one-parameter lookup tool. Combined with the fully documented parameter, an agent has enough to call it correctly, though freshness and id-sourcing guidance are absent.

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 coverage is 100% for the sole product_id parameter, so the baseline is 3. The description adds only mild specificity ('one product repository id', singular), and does not explain the id format or where to obtain it, so it adds little beyond the schema.

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 description states a specific verb and resource ('Get Dollar Tree product prices') and names the returned fields (list price, per-SKU prices, price-range flag). It is clear what the tool does, though it never names the sibling dollartree_product or dollartree_stock_status to say how it differs from them.

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: 'for one product repository id' signals that a single product id is required, and the sibling set implies that id comes from dollartree_search or dollartree_product. There is no explicit statement of when to choose this over dollartree_product or that it does not accept search terms or lists of ids.

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