Skip to main content
Glama

darioa: websites, booking sites, webshops and web apps

Get the product and price for a need

get_quote
Read-only

Maps what the user needs to one product and returns its prices (once, yearly, first year, excluding 21% VAT), what is included and when they pay. Describe the need in plain words (Dutch or English) and/or pass features. If the need is unclear it asks questions instead of guessing; if it is outside the four products (for example an app for the App Store) it returns no price. Prices come only from the public price list. An indication, not a binding offer. No side effects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
needNoWhat the user needs, in their words (notes), for example: a website for my taxi company where customers can book rides. Required unless product is given.
localeNoLanguage of the text in the result. Prices are the same in both. Default en.
productNoOptional: the product id (website, booking, webshop, webapp) to get its fixed price for. When given, it decides the product.
featuresNoOptional: what the site must do, from this list. The most capable feature decides the product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / need / description
      Previous value: -"What the user needs, in their words. For example: a website for my taxi company where customers can book rides."New value: +"What the user needs, in their words (notes), for example: a website for my taxi company where customers can book rides. Required unless product is given."
    • addedInput schema / properties / product
      Added value: +{
      +  "description": "Optional: the product id (website, booking, webshop, webapp) to get its fixed price for. When given, it decides the product.",
      +  "enum": [
      +    "website",
      +    "booking",
      +    "webshop",
      +    "webapp"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "need"
      -]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint=false, the description discloses the return shape (three price cadences, VAT excluded, inclusions, payment timing), the ambiguity behavior (asks questions rather than guessing), the out-of-scope outcome (no price), the data source (public price list only), and the non-binding nature of the quote. That is substantial context the annotations cannot convey.

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?

The core action and its output are front-loaded, and each subsequent sentence adds a distinct fact (input form, ambiguity handling, out-of-scope result, price source, disclaimer). It is dense but a touch overlong, and the closing 'No side effects' largely restates the annotations.

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?

With four all-optional parameters and no output schema, the description carries the burden of explaining results and does so fully: price periods, VAT treatment, inclusions, payment timing, and the no-result case. Nothing essential for correct invocation is missing.

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%, so the schema already documents all four parameters and their enums. The description still adds value by explaining the interaction between them — the need may be free text in Dutch or English and/or features may be supplied, with features determining the product — which is a slight step beyond the field-level text.

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 and resource: maps a user need to exactly one of four products and returns prices (once, yearly, first year, excluding 21% VAT), what is included, and when payment happens. Concrete enough that an agent can distinguish it from list_products (catalog lookup) or request_contact without opening either schema.

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?

Gives clear context for use — describe the need in plain words (Dutch or English) and/or pass features — and a when-not case: needs outside the four products, such as an App Store app, get no price. It does not name sibling tools or say explicitly to use list_products for browsing instead, so it stops short of the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.