Skip to main content
Glama

Price a modern classic pergola kit

quote_modern_classic_pergola

Price a modern classic Baldwin fiberglass pergola kit (four columns with an aluminum-look finish and hat trim): pre-engineered and custom crafted, with all hardware, instructions, and a high-end factory paint finish. The structure stays the same while the trim adjusts in three architecture steps: classic (Greco-Roman), modern classic, and modern. 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": {
      "width_in": "<width_in>",
      "depth_in": "<depth_in>"
    },
    "name": "quote_modern_classic_pergola"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoPaint color. "custom" is not currently priceable online for modern classic.white
shadeNo1 includes the retractable shade in the saved design. 0 leaves it off.
dentilsNoInclude dentil molding. Adds $5 per dentil to the price.
ai_modelNoExact model only if actually known; otherwise omit. Do not infer it from the application.
depth_inYesDepth in inches, column center-to-center.
width_inYesWidth in inches, column center-to-center.
ai_clientNoAI application when known, e.g. ChatGPT or Claude. Client-reported; do not guess.
height_inNoColumn height in inches.
project_idNoThe project_id returned by an earlier call in this conversation. Reuse it so the summary stays with the same project.
project_useNoGeneric stated purpose, e.g. church gathering area or family patio. No individual or organization names.
shade_colorNoRetractable shade fabric name, for example Sunbrella Oyster 4642.
architectureNoArchitectural style, set by trim only; the structure stays the same. classic is Greco-Roman, modern_classic is the middle step, modern is the most contemporary.modern_classic
column_styleNoColumn size and shape. 10recessed and 12recessed add $400 for each of the four columns and are a special order based on site conditions.10square
project_typeNoresidential, commercial, institutional, or unknown. A church/school project is institutional, not a statement about personal beliefs.
project_regionNoStated state/province/region, e.g. Nebraska. No street address or precise location.
sconce_percentNoSconce preview level, 0 to 100. Keep this on a saved design link.
shade_positionNoWhether the saved shade is extended or retracted.
project_countryNoCountry of the project when stated or unambiguously established. No IP-based guesses.
fanlight_percentNoFan-light preview level. The saved modern classic link names this fanLight.
purlin_spacing_inNoDesired purlin spacing in inches on-center.
rafter_spacing_inNoDesired rafter spacing in inches 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. Changed6 schema fields changed
    • addedInput schema / properties / column_style
      Added value: +{
      +  "default": "10square",
      +  "description": "Column size and shape. 10recessed and 12recessed add $400 for each of the four columns and are a special order based on site conditions.",
      +  "enum": [
      +    "10round",
      +    "12round",
      +    "10square",
      +    "12square",
      +    "10recessed",
      +    "12recessed"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / fanlight_percent
      Added value: +{
      +  "description": "Fan-light preview level. The saved modern classic link names this fanLight.",
      +  "maximum": 100,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / sconce_percent
      Added value: +{
      +  "description": "Sconce preview level, 0 to 100. Keep this on a saved design link.",
      +  "maximum": 100,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / shade
      Added value: +{
      +  "description": "1 includes the retractable shade in the saved design. 0 leaves it off.",
      +  "enum": [
      +    0,
      +    1
      +  ],
      +  "type": "integer"
      +}
    • addedInput schema / properties / shade_color
      Added value: +{
      +  "description": "Retractable shade fabric name, for example Sunbrella Oyster 4642.",
      +  "type": "string"
      +}
    • addedInput schema / properties / shade_position
      Added value: +{
      +  "description": "Whether the saved shade is extended or retracted.",
      +  "enum": [
      +    "extended",
      +    "retracted"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the price matches the live 3D configurator, it is a budgetary estimate and not a binding quote, and electrical, installation, shipping, footings, permits and tax are quoted separately. With no output schema, it also carries return-value information by naming design_url and the fallback configurator_url, so an agent knows what comes back and how to present it.

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 is front-loaded, but the text is long and blends tool definition with agent behavior scripting (hyperlink vs button, no sidebar/modal/iframe, introduce user controls) plus marketing copy about aluminum-look finish and hat trim. Several sentences serve conversational policy rather than helping select or invoke this tool.

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 22-parameter, no-output-schema pricing tool, it covers the essentials: accompanying sequence (get_pergola_guidance), defaults-based estimating, non-binding pricing, separately quoted add-ons, and the design_url/configurator_url return path. Some return detail (e.g., price breakdown fields) is left implicit, but the agent has enough to call it and present results correctly.

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 baseline is 3, but the description adds interpretive meaning: width/depth are column center-to-center and the agent should explain support-center versus overall roof dimensions, and the architecture enum maps to three named trim steps with an unchanged structure. These clarifications reduce misconfiguration of the most important dimensional inputs.

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?

Names a specific verb and resource — pricing a modern classic Baldwin fiberglass pergola kit — and describes the product scope (four columns, hat trim, factory paint, three trim-based architecture steps). It is clear what the tool computes, but it never states how this differs from quote_classic_pergola even though the architecture enum accepts 'classic' and 'modern' here, leaving the boundary between the two pricing tools ambiguous.

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 explicit workflow: call get_pergola_guidance first, then with attachment and approximate size offer a starting estimate using stated defaults, and continue discussing preferences afterward. It also spells out presentation rules (hyperlink the design_url, never open or embed the configurator). The one gap is no explicit when-to-use-this-instead-of-quote_classic_pergola or quote_curved_pergola guidance.

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