Skip to main content
Glama

Price a curved pergola kit

quote_curved_pergola

Price a curved Baldwin fiberglass pergola kit (arc-based geometry): pre-engineered and custom crafted, with all hardware, instructions, and a high-end factory paint finish. Returns the same price shown on the live 3D configurator. Budgetary estimate, not a binding quote. Optional electrical, installation, shipping, footings, permits, and tax are quoted separately. Call get_pergola_guidance first. With attachment and approximate size, offer a starting estimate using stated defaults; continue discussing preferences afterward. Explain support-center versus overall roof dimensions. Present the returned design_url, or the full configurator_url if design_url is absent, as a clickable text hyperlink to Baldwin website, or a button if supported. Do not automatically open or embed the configurator in a sidebar, modal, iframe, or in-chat portal. Introduce the available user controls.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "radius_ft": "<radius_ft>",
      "arc_deg": "<arc_deg>",
      "depth_ft": "<depth_ft>"
    },
    "name": "quote_curved_pergola"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNoRafter tail profile.windsor
colorNoPaint color.white
mountNoMounting surface. Does not affect the kit price.Concrete Footings
arc_degYesArc angle in degrees. 360 is a full circle.
ai_modelNoExact model only if actually known; otherwise omit. Do not infer it from the application.
depth_ftYesDepth in feet, front row to back row. Use 0 for a curved colonnade.
ai_clientNoAI application when known, e.g. ChatGPT or Claude. Client-reported; do not guess.
back_colsNoBack row column count. Use 0 for a curved colonnade.
radius_ftYesInner radius of the arc in feet.
front_colsNoFront row column count.
project_idNoThe project_id returned by an earlier call in this conversation. Reuse it so the summary stays with the same project.
bearing_degNoCompass bearing in degrees (0 = north). Affects sun simulation only, not price.
project_useNoGeneric stated purpose, e.g. church gathering area or family patio. No individual or organization names.
column_styleNoColumn diameter and shape. 10recessed and 12recessed add $400 per column and are a special order based on site conditions. The curved builder uses colType 10rec or 12rec.10square
project_typeNoresidential, commercial, institutional, or unknown. A church/school project is institutional, not a statement about personal beliefs.
col_height_ftNoColumn height in feet. Stock comes in 8/10/12 ft; pricing rounds up.
project_regionNoStated state/province/region, e.g. Nebraska. No street address or precise location.
project_countryNoCountry of the project when stated or unambiguously established. No IP-based guesses.
purlin_spacing_ftNoDesired purlin spacing in feet on-center.
rafter_spacing_ftNoDesired rafter spacing in feet on-center.
conversation_summaryNoFactual project summary under 1,500 characters: stated goals, use, architecture, accessories, alternatives and open design questions. Distinguish requests from ideas discussed. Exclude names, contact details, exact addresses, sensitive personal facts and inferences about wealth or willingness to pay. Saved for later contact submission; not yet delivered to sales. Follow host disclosure rules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / column_style / description
      Previous value: -"Column diameter and shape."New value: +"Column diameter and shape. 10recessed and 12recessed add $400 per column and are a special order based on site conditions. The curved builder uses colType 10rec or 12rec."
    • changedInput schema / properties / column_style / enum
      Previous value: -[
      -  "10round",
      -  "12round",
      -  "10square",
      -  "12square"
      -]New value: +[
      +  "10round",
      +  "12round",
      +  "10square",
      +  "12square",
      +  "10recessed",
      +  "12recessed"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false, which says little about pricing behavior. The description adds substantial context beyond that: the result mirrors the live 3D configurator, it is a budgetary estimate and not a binding quote, and electrical/installation/shipping/footings/permits/tax are quoted separately. It also discloses what is returned (design_url, fallback configurator_url) in the absence of an output schema, though it does not describe the price breakdown or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and pricing caveats are front-loaded, which is good. However, the back half is a dense run of post-call UX directives (hyperlink text rules, button fallback, no sidebar/modal/iframe/in-chat embedding, introduce available user controls) that mix presentation policy with tool semantics and lengthen the definition considerably for a single call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 21-parameter, non-idempotent, no-output-schema tool, the description covers the prerequisites, the estimate-versus-quote distinction, optional line items, and the returned URLs, which is what an agent most needs. It is slightly incomplete on what the price payload actually contains (line items, currency, validity window) and on invalid-input behavior.

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?

Schema description coverage is 100%, so enums, defaults, ranges, and field meaning are already fully documented in the schema. The description adds only one semantic note relevant to parameters, that support-center versus overall roof dimensions must be explained to the user. Baseline 3 applies since the schema does the heavy lifting.

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: "Price a curved Baldwin fiberglass pergola kit (arc-based geometry)". The adjectives "curved" and "arc-based" plus the explicit geometric scope (radius/arc/depth) distinguish it from the linear siblings quote_classic_pergola and quote_modern_classic_pergola without the agent needing to open a 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 an explicit sequencing prerequisite ("Call get_pergola_guidance first") and a concrete invocation pattern: with attachment plus approximate size, offer a starting estimate using stated defaults, then keep discussing preferences. This is clear when-to-use guidance. It stops short of explicitly contrasting with the non-curved quoting siblings, so a 4 rather than 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.

Resources