get_productGet a SaaS product's current pricing plans and its most recent price changes. Call this when the user asks what a specific product costs, what plans it offers, or whether its price changed recently. Takes the product slug (find it with search_products). Shows the 10 most recent changes; deeper history requires a free PriceTrack API key.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Product slug, e.g. "notion" |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds context beyond the readOnlyHint=true annotation by noting the tool shows only the 10 most recent changes and that deeper history requires a free API key. It does not contradict the annotation (readOnlyHint=true is consistent with a query). No contradictory annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, no wasted words. Each sentence serves a distinct purpose: stating what the tool does, when to use it (with prerequisite), and a behavioral constraint (history limit). Front-loaded with the core action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool (1 param, no output schema, high schema coverage, single sibling differentiation), the description is complete. It covers purpose, usage context, parameter origin, and a critical limitation (10 recent changes, deeper history requires API key). No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already has full coverage (100% of param has a description), so baseline is 3. The description adds extra meaning by explaining how to obtain the slug via 'search_products' and including a real example ('notion'), which helps the agent use the parameter correctly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'get' and the specific resources: 'pricing plans' and 'most recent price changes'. It distinguishes itself from siblings by focusing on a single product's pricing and changes, whereas siblings like 'compare_products' and 'recent_price_changes' handle broader comparisons or lists.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool: 'Call this when the user asks what a specific product costs, what plans it offers, or whether its price changed recently.' It also directs the user to find the slug with 'search_products', providing clear prerequisites and alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, distinct purpose: searching, fetching details, comparing, history, recent changes, alerts, stack, and list. No two tools appear to overlap in functionality, making selection unambiguous.
Most tools follow a verb_noun pattern (compare_products, create_price_alert, get_price_history, get_product, get_stack, list_alerts, search_products), but recent_price_changes breaks the pattern as an adjective_noun. Minor inconsistency but still predictable.
8 tools is well-scoped for a price tracking service, covering search, detailed lookups, comparisons, history, alerts, and user-specific views without unnecessary bloat.
Core workflows are covered: search, view details, compare, get history, set alerts, and view tracked stack. Missing update/delete alert operations and a way to manage tracked products directly, but these are minor gaps agents can work around.