Skip to main content
Glama

Pergola questions and answers

search_pergola_faq
Read-onlyIdempotent

Search Baldwin Pergolas questions and answers on size, height, foundations and existing patios or decks, customization, accessories, and what to consider before buying. Answers are written for homeowners; share them in a warm, consultative voice and use any ask_next questions to continue the conversation.

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": "search_pergola_faq"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of answers to return.
queryNoWhat the person asked, in plain words. Example: "how tall should it be". Omit to list the available questions.
categoryNoOptional topic filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "accessories",
      -  "customization",
      -  "foundation",
      -  "height",
      -  "planning",
      -  "sizing"
      -]New value: +[
      +  "accessories",
      +  "customization",
      +  "foundation",
      +  "height",
      +  "planning",
      +  "services",
      +  "sizing"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the audience (homeowners), the required response voice (warm, consultative), and the presence of an ask_next field in results that should drive follow-up questions — details an agent could not get from annotations or schema.

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 verb and resource are front-loaded, and the topic list doubles as scope documentation rather than filler. The second sentence on voice and ask_next is compact, though the topic enumeration is long enough to push the definition toward a single dense sentence.

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 read-only, three-parameter search tool with no output schema and full schema coverage, the description supplies the missing pieces: search scope, target audience, answer style, and the ask_next follow-up mechanism. Only the explicit routing versus sibling knowledge tools is absent.

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 description coverage is 100%, so the baseline is 3. The description earns an extra point by enumerating the topical scope (size, height, foundation, patios/decks, customization, accessories, planning), which maps onto the category enum and helps the agent choose a filter and phrase the query.

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 opens with a specific verb and resource ("Search Baldwin Pergolas questions and answers") and enumerates the covered topics (size, height, foundations, patios/decks, customization, accessories, buying considerations). This clearly signals an FAQ search tool, though it never names how it differs from the sibling FAQ/knowledge tools such as search_pergola_knowledge or get_pergola_guidance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied by "Answers are written for homeowners" and by the instruction to continue with ask_next questions, which tells the agent this is a conversational FAQ retrieval step. However, there is no explicit when-to-use vs. when-not-to-use guidance relative to the knowledge/guidance siblings, and the important behavior of omitting query to list questions lives only in the schema.

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