Skip to main content
Glama

Get Price Quote

get_quote
Idempotent

Return a price quote for a service at a business. Exact configured prices may create a time-limited offer; unmatched requests use a third-party AI estimate that is not firm merchant pricing and must be confirmed with the business. Use this when a user asks 'how much does X cost?' or 'what's the price for Y?'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesBusiness slug identifier
paramsNoOptional service parameters (e.g., {size:'large'})
serviceYesRequested service name to quote

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
offerYesServer-minted immutable price offer — only exact configured prices mint one; estimates and ranges never do.
quoteYes
reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / params / additionalProperties / maxLength
      Added value: +200
    • addedInput schema / properties / params / propertyNames / maxLength
      Added value: +64
  2. Changed2 schema fields changed
    • addedOutput schema / properties / offer
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "expires_at": {
      +          "description": "Offer expiry (Unix seconds); the quoted price is guaranteed until then",
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "key_id": {
      +          "type": "string"
      +        },
      +        "offer_id": {
      +          "type": "string"
      +        },
      +        "version": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "offer_id",
      +        "version",
      +        "key_id",
      +        "expires_at"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Server-minted immutable price offer — only exact configured prices mint one; estimates and ranges never do."
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "quote"
      -]New value: +[
      +  "quote",
      +  "offer"
      +]
  3. Changed6 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / params / description
      Previous value: -"optional service parameters (e.g., {size:'large'})"New value: +"Optional service parameters (e.g., {size:'large'})"
    • addedInput schema / properties / params / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / service / description
      Previous value: -"requested service name"New value: +"Requested service name to quote"
    • changedInput schema / properties / slug / description
      Previous value: -"business slug"New value: +"Business slug identifier"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "quote": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "basis": {
      +              "enum": [
      +                "pricing_json_v2",
      +                "llm_estimate"
      +              ],
      +              "type": "string"
      +            },
      +            "confidence": {
      +              "enum": [
      +                "exact",
      +                "range",
      +                "estimate"
      +              ],
      +              "type": "string"
      +            },
      +            "currency": {
      +              "type": "string"
      +            },
      +            "disclaimer": {
      +              "type": "string"
      +            },
      +            "high": {
      +              "type": "number"
      +            },
      +            "low": {
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "low",
      +            "high",
      +            "currency",
      +            "confidence",
      +            "basis"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "reason": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "quote"
      +  ],
      +  "type": "object"
      +}
  4. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / params / description
      Previous value: -"Optional service parameters (e.g., {size:'large'})"New value: +"optional service parameters (e.g., {size:'large'})"
    • removedInput schema / properties / params / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • changedInput schema / properties / service / description
      Previous value: -"Requested service name to quote"New value: +"requested service name"
    • changedInput schema / properties / slug / description
      Previous value: -"Business slug identifier"New value: +"business slug"
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "quote": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": false,
      -          "properties": {
      -            "basis": {
      -              "enum": [
      -                "pricing_json_v2",
      -                "llm_estimate"
      -              ],
      -              "type": "string"
      -            },
      -            "confidence": {
      -              "enum": [
      -                "exact",
      -                "range",
      -                "estimate"
      -              ],
      -              "type": "string"
      -            },
      -            "currency": {
      -              "type": "string"
      -            },
      -            "disclaimer": {
      -              "type": "string"
      -            },
      -            "high": {
      -              "type": "number"
      -            },
      -            "low": {
      -              "type": "number"
      -            }
      -          },
      -          "required": [
      -            "low",
      -            "high",
      -            "currency",
      -            "confidence",
      -            "basis"
      -          ],
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "reason": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "quote"
      -  ],
      -  "type": "object"
      -}New value: +null
  5. Changed6 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / params / description
      Previous value: -"optional service parameters (e.g., {size:'large'})"New value: +"Optional service parameters (e.g., {size:'large'})"
    • addedInput schema / properties / params / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / service / description
      Previous value: -"requested service name"New value: +"Requested service name to quote"
    • changedInput schema / properties / slug / description
      Previous value: -"business slug"New value: +"Business slug identifier"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "quote": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "basis": {
      +              "enum": [
      +                "pricing_json_v2",
      +                "llm_estimate"
      +              ],
      +              "type": "string"
      +            },
      +            "confidence": {
      +              "enum": [
      +                "exact",
      +                "range",
      +                "estimate"
      +              ],
      +              "type": "string"
      +            },
      +            "currency": {
      +              "type": "string"
      +            },
      +            "disclaimer": {
      +              "type": "string"
      +            },
      +            "high": {
      +              "type": "number"
      +            },
      +            "low": {
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "low",
      +            "high",
      +            "currency",
      +            "confidence",
      +            "basis"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "reason": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "quote"
      +  ],
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description goes beyond the annotations by disclosing that exact configured prices may create a time-limited offer, and that unmatched requests use a third-party AI estimate that is not firm merchant pricing and must be confirmed. This is valuable behavioral context beyond readOnlyHint and idempotentHint.

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 three sentences with no filler. It front-loads the core purpose, then adds the critical caveat about pricing behavior, and finally gives a practical usage trigger. Every sentence contributes meaningful information.

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?

The description, combined with the rich schema, output schema presence, and annotations, provides enough context for an agent to call the tool correctly. It explains what the tool does, when to use it, and the important caveat that some quotes are non-binding estimates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already has 100% description coverage for slug, service, and params, so the description does not need to repeat parameter details. The description adds no additional parameter-level meaning beyond the schema, placing it at the baseline for well-covered schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool returns a price quote for a service at a business, using a specific verb and resource. It does not explicitly distinguish itself from sibling tools like submit_quote_request or list_services, so it stops short of full differentiation.

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 provides explicit usage guidance: 'Use this when a user asks how much does X cost?' This gives clear context for when the tool is appropriate. However, it does not mention when not to use it or point to alternatives, so it earns a 4 rather than a 5.

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.