Baldwin Pergolas

Price lattice panel supports

quote_lattice_panel

Price the support posts for a Baldwin lattice privacy panel (panel material is priced separately). 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 exact returned configurator_url 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": {
      "panel_width_ft": "<panel_width_ft>",
      "panel_height_ft": "<panel_height_ft>"
    },
    "name": "quote_lattice_panel"
  }
}

Input Schema

Name	Required	Description	Default
`color`	No	Paint color.	white
`ai_model`	No	Exact model only if actually known; otherwise omit. Do not infer it from the application.
`ai_client`	No	AI application when known, e.g. ChatGPT or Claude. Client-reported; do not guess.
`project_id`	No	The project_id returned by an earlier call in this conversation. Reuse it so the summary stays with the same project.
`anchor_type`	No	post_mount prices support posts; wall_mount prices zero supports.	post_mount
`project_use`	No	Generic stated purpose, e.g. church gathering area or family patio. No individual or organization names.
`project_type`	No	residential, commercial, institutional, or unknown. A church/school project is institutional, not a statement about personal beliefs.
`support_type`	No	Support post material and size in inches, e.g. fiberglass_8.	fiberglass_8
`panel_width_ft`	Yes	Panel width in feet.
`project_region`	No	Stated state/province/region, e.g. Nebraska. No street address or precise location.
`panel_height_ft`	Yes	Panel height in feet.
`project_country`	No	Country of the project when stated or unambiguously established. No IP-based guesses.
`support_height_ft`	No	Support height in feet. Heights above 8 ft add a per-foot charge.
`conversation_summary`	No	Factual 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.

First observedNov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent, closed-world call, and the description adds real value on top: the result is a 'budgetary estimate, not a binding quote', and there are explicit presentation constraints (hyperlink the returned configurator_url, never auto-open or embed it in a sidebar, modal, iframe, or in-chat portal). What it does not explain is why the call is stateful/non-read-only (project_id reuse and summary persistence), which is the one annotation an agent might misread.

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?

Front-loaded with the pricing scope, then the prerequisites, then the presentation rules, so an agent reads the essential part first. It is on the long side at eight sentences and mixes pricing semantics with chat-rendering etiquette, but each sentence carries a distinct instruction rather than restating the title.

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 14-parameter, non-read-only quoting tool with no output schema, the description covers scope, prerequisites, estimate-vs-quote caveat, and the one return artifact that matters (configurator_url). Gaps are modest: it never states the currency/units of the returned price or confirms that project_id reuse is what makes the call stateful.

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 baseline is 3, but the description adds meaning beyond the schema by telling the agent to price 'with attachment and approximate size' using 'stated defaults' and to 'explain support-center versus overall roof dimensions' -- clarifying the dimensional convention the raw 'Panel width in feet' / 'Panel height in feet' fields leave ambiguous. The remaining 12 parameters are carried entirely by their own schema descriptions.

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 the support posts for a Baldwin lattice privacy panel' -- and immediately scopes it with '(panel material is priced separately).' That parenthetical alone separates it from the sibling quote_* tools that price whole pergolas, so an agent can pick correctly without opening 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 a concrete prerequisite ('Call get_pergola_guidance first') and a procedural path: offer a starting estimate from stated defaults, then continue the conversation about preferences. It also lists what is out of scope (electrical, installation, shipping, footings, permits, tax quoted separately). It stops short of naming when a different quote_* sibling would be the better choice, which keeps it below a 5.

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

All Baldwin Pergolas tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?