get_odoo_pricingReturn current Odoo license list pricing (Standard and Custom tiers, USD and CAD) and Odoo.sh hosting rates from the single Octura pricing source, plus links to the pricing page and cost calculators. Implementation is quoted per project.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden for behavioral disclosure. It uses 'Return' to imply a read-only operation and discloses that data comes from a single source and that links to calculators are included. However, it does not explicitly state that there are no side effects, whether network calls are made, if results are cached, or any potential prerequisites, leaving some informational gaps.
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?
The description is two sentences, front-loaded with the primary action, and includes only relevant details. It packs the required information without fluff. The second sentence about implementation quoting is a useful caveat that doesn't bloat the text.
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 tool's simplicity (no parameters, no output schema), the description effectively enumerates what the tool returns: pricing tiers, currencies, hosting rates, links, and the implementation caveat. It provides sufficient context for an agent to understand the scope, though it could clarify the output format or data freshness for complete coverage.
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 tool has zero parameters, so the input schema is complete and the description has no need to explain parameters. As per the rubric, 0 params receives a baseline of 4. The description does not add any parameter-related meaning because none exist, but nothing is missing either.
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 tool returns current Odoo license list pricing (Standard/Custom, USD/CAD) and Odoo.sh hosting rates, plus links to pricing page and calculators. It identifies the specific verb ('Return'), the resource ('Odoo license list pricing' and 'Odoo.sh hosting rates'), and the source ('single Octura pricing source'), effectively distinguishing it from sibling calculator tools.
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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention any alternative tool names, exclusions, or specific contexts for use. The only hint is the phrase 'single Octura pricing source,' which implies it's the canonical source, but there is no direct 'use this when' statement.
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.
Several tool pairs overlap: find_odoo_apps_for and odoo-app-selector are near-duplicates, compare_odoo_vs and erp-selection-tool both address ERP choice, and multiple Odoo cost calculators (TCO, ROI, stack savings) have blurry boundaries.
Names mix snake_case (ask_octura, get_odoo_pricing) and hyphens (canadian-sales-tax-calculator), and vary from verb-first to noun-first, with inconsistent suffixes like calculator/estimator/tool/checker.
At 29 tools, the server is overloaded. Many are narrowly-focused calculators that could be consolidated, and the duplicate app selector inflates the count.
The set covers the core Octura/Odoo workflows well: content retrieval, pricing, partner info, cost estimation across the Odoo lifecycle, tax and inventory calculations. Minor gaps exist (e.g., no support costs beyond TCO, no contact form tool), but agents can work around them.