TaskRail

find_best_total_deal

Find the cheapest price and best deal for an exact new physical product. Use for requests like “where to buy,” “price comparison,” “lowest total cost including shipping,” or “is it in stock?” It resolves the model and variant, checks current offers, shipping, stock, delivery timing, and known mandatory fees.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`product`	Yes	Exact product name, model, and variant in the user's own words
`postal_code`	No	US postal code for delivery price and availability

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`status`	Yes
`decision`	Yes
`freshness`	Yes
`confidence`	Yes
`limitations`	Yes
`source_names`	Yes
`best_price_usd`	No
`recommendation`	Yes
`sources_failed`	Yes
`sources_checked_count`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=false and openWorldHint=true; the description adds valuable context about what is checked (offers, shipping, stock, delivery, fees), but does not contradict annotations.

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 description is two sentences, front-loaded with purpose, and every sentence adds value without redundancy.

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?

Given the presence of an output schema and the clear coverage of purpose, triggers, and checks, the description is fully adequate for the tool's complexity.

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 description adds meaning to the 'product' parameter by specifying it should be 'in the user's own words', going beyond the schema's minimal description.

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 uses a specific verb ('Find') and resource ('cheapest price and best deal') for 'exact new physical product', and lists example queries that clearly distinguish it from sibling tools like find_used_or_refurbished_alternatives.

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?

The description explicitly states use cases ('where to buy', 'price comparison', etc.) and what it resolves (model/variant, offers, shipping), but does not explicitly state when not to use it, relying on context from sibling tools.

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

All TaskRail tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool covers a distinct purpose: compatibility checking, new product deals, used alternatives, and task procedures. No overlap in functionality, and descriptions clearly differentiate them.

Naming Consistency4/5

All names use snake_case with a verb-noun pattern, e.g., check_products_compatibility, find_best_total_deal. Minor variance in noun phrase length (e.g., find_used_or_refurbished_alternatives is longer) but overall consistent.

Tool Count4/5

With only 4 tools, the set is compact but focused. It covers the core actions for product shopping and task guidance without unnecessary bloat. Could benefit from a broader scope, but count is reasonable for the niche.

Completeness4/5

The tools cover key product lifecycle phases: compatibility, new and used purchasing, and after-sales tasks. Missing general product search or reviews, but the core workflow (compare, buy, complete task) is well-served.

Resources

Need Help?