Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

dollartree_price

Read-only

Get current Dollar Tree price data for one product id: the overall list value, whether it is a range, and each SKU's list and sale price. Use product_id from dollartree_search or dollartree_product; choose this for pricing-only lookups and dollartree_product for the full product record. An unknown numeric id returns not found.

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>"
    },
    "name": "dollartree_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesRequired. One Dollar Tree product repository id returned by dollartree_search.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds the failure behavior ('An unknown numeric id returns not found') and describes what the payload contains (range flag, per-SKU list vs sale price). No mention of rate limits or partial-data caveats, so short of a 5.

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?

Three sentences, each earning its place: payload summary first, provenance/routing second, error behavior last. No filler or restatement of the name.

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

Completeness5/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 values needn't be enumerated in prose, and annotations cover the read-only profile. Combined with the payload sketch, the sibling routing, and the not-found behavior, an agent has everything needed to call it correctly.

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% and the parameter is fully described there, so baseline is 3. The description adds that exactly one id is accepted and extends the provenance beyond the schema by allowing ids from either dollartree_search or dollartree_product.

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 ('Get') and resource ('current Dollar Tree price data') plus the exact return contents (overall list value, range flag, per-SKU list and sale price). It also names the sibling dollartree_product and the boundary between them, so an agent can distinguish them without opening 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?

Explicitly routes the agent: use product_id from dollartree_search or dollartree_product, and 'choose this for pricing-only lookups and dollartree_product for the full product record.' Both the source and the alternative case are named.

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

All Crawlora MCP toolsInspect
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