Skip to main content
Glama

OhGiftPlease Gift Discovery

SearchInSite

Searches the site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp) for information. Use this tool ONLY in the following cases:

  1. You just used "GetBusinessDetails" tool and you did not find the information you need.

  2. User asked a generic business question about their business (e.g., business address, business hours, contact information, return policy, etc.)

  3. You already tried to find an entity (e.g., product, service, etc.) using an API tool and you did not find the information you need.

  4. The request is too vague and you do not know what type of entity it is and what to search for in the docs. Do NOT use this tool for searching for products or other offered services - use the 'SearchSiteApiDocs' tool instead (unless you already tried that tool and you did not find the information you need). This tool DOES NOT support filters - you cannot ask questions like "find me something under $10". This tool searches the site's regular pages and blog posts. It does NOT cover pages generated from CMS collections (dynamic item pages). When the site has such pages, the result starts with their paths and how to list the pages under each one.

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": {
      "searchTerm": "<searchTerm>"
    },
    "name": "SearchInSite"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchTermYesThe term to search for in the site, e.g. "working hours" or "store locations"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses important traits: no filter support, coverage of regular pages and blog posts only, exclusion of CMS-generated dynamic item pages, and how such pages appear in results. It does not describe rate limits or auth requirements, but it covers the main behavioral constraints an agent needs.

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 description is front-loaded with purpose and then structured as numbered usage cases followed by exclusions and scope limits. It is somewhat long, but the length is justified by the routing rules and behavioral constraints.

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 one-parameter search tool with no output schema or annotations, the description is reasonably complete. It explains scope, exclusions, unsupported filters, and CMS page behavior, though it could say more about return values or authentication.

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%, and the searchTerm parameter already includes examples. The description adds useful context that filters are not supported, but it does not add meaning about the parameter beyond what the schema provides.

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?

The description states a specific verb and resource: searching the OhGiftPlease site for information. It clearly distinguishes this tool from SearchSiteApiDocs and GetBusinessDetails, so an agent can identify its role without opening the schema.

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?

It gives explicit conditions for when to use the tool and when not to use it, including fallback cases after GetBusinessDetails or API tools fail. It also names the alternative SearchSiteApiDocs for product or service searches and states that filters are unsupported.

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.