Skip to main content
Glama

OhGiftPlease Gift Discovery

by io.github.racharmi
OverviewDiscussionsAdmin

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".

Input Schema

TableJSON 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?

No annotations are provided, so the description carries the burden. It discloses a genuinely important behavioral constraint — the tool DOES NOT support filters (e.g., 'under $10') — which is not derivable from the schema. It stops short of describing return format, result ranking, or auth requirements, so it is not fully complete.

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 intent and the four use cases are front-loaded, and the exclusion follows the inclusions in a logical order. The parenthetical in item 4 and the slight overlap between items 1 and 3 add minor redundancy but each sentence still earns its place.

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 single-parameter, no-output-schema search tool, the description covers purpose, precedence against GetBusinessDetails and API tools, and the no-filter limitation. It could note that results are free-text site content, but nothing critical to invocation is missing.

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 the single searchTerm parameter is well documented with examples ('working hours', 'store locations'). The description adds no syntax or format detail beyond the schema, so baseline 3 is appropriate.

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 (searches) and resource (the site 'OhGiftPlease') with the exact endpoint, and explicitly contrasts itself with the sibling 'SearchSiteApiDocs'. An agent can distinguish it from siblings without opening any 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?

Provides four enumerated when-to-use cases plus an explicit when-not-to-use rule naming the alternative tool to use instead for product/service searches. Nothing about routing is left to inference.

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

All OhGiftPlease Gift Discovery toolsInspect
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