Skip to main content
Glama

Remodel Your Vibe Site Guide

Search the website

search_site
Read-onlyIdempotent

Find pages on remodelyourvibe.com by keyword. Searches all services, service-by-city pages, service areas and remodeling articles, and returns each match's title, URL, section and a one-sentence summary. Use it first to locate the right page, then read that page with fetch_page.

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": {
      "query": "<query>"
    },
    "name": "search_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
queryYesKeywords to look for, for example "pool remodel cost Orange County" or "ADU permit Pasadena".
sectionNoOptional. Restrict results to one part of the site.

Output Schema

NameRequiredDescriptionDefault
countYes
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds valuable scope context about which site sections are indexed. It does not state result ordering/relevance or what happens when nothing matches, which are the remaining behavioral gaps for a search tool.

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?

Two compact sentences, front-loaded with purpose and followed by the workflow instruction. No filler, hedging, or repetition of 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 three-parameter read-only search with a full schema and an output schema, the description covers purpose, corpus, and workflow, which is enough to call it correctly. Minor omissions: no mention of result ranking or empty-result behavior, and the enumerated return fields partly duplicate the output schema.

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 coverage is 100% and each parameter (query, limit, section enum) is already documented with examples and bounds in the schema. The description adds only the general notion of keyword search and notes the section taxonomy, not parameter-level meaning, so baseline 3 applies.

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 ("Find pages on remodelyourvibe.com by keyword") and enumerates the corpus searched: services, service-by-city pages, service areas, and remodeling articles. This clearly distinguishes it from the sibling fetch_page, which reads a single already-located page.

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

Usage Guidelines5/5

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

Gives an explicit ordering rule ("Use it first to locate the right page") and names the follow-up alternative with its condition ("then read that page with fetch_page"). The agent knows both when to use this tool and what to do next.

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