Skip to main content
Glama

Lowtoxgear Storefront

by com.lowtoxgear

search_products

Search the Lowtoxgear catalogue by keyword. Australian low-tox lifestyle brand spanning certified activewear, clean supplements, GOTS-organic apparel, and low-tox home goods. Returns up to 10 product summaries with title, price (AUD), image, availability, and storefront URL. Natural-language queries work: "organic cotton tee", "PFAS-free duffel", "snow bibs", "magnesium supplement".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo1–10. Default 10.
queryYesFree-text keyword or phrase

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It describes return format (up to 10 summaries with specific fields) and accepts natural language. Does not mention auth, rate limits, or side effects, but search is generally non-destructive.

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 well-structured sentences: first states core purpose and context, second details return format and query examples. No redundant or unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with two parameters and no output schema, description fully covers inputs, behavior, and outputs. Examples provide clarity on usage. No gaps identified.

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%, but description adds value by explaining natural-language queries work and listing example queries. Also clarifies limit range and default, which are already in schema but reinforced.

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?

Description clearly states the tool searches the Lowtoxgear catalogue by keyword, mentions brand and product categories, and lists return fields. Distinguishes from siblings like filter_by_certification and list_collections by focusing on keyword search.

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?

Provides context on natural-language queries and examples. Does not explicitly exclude alternative tools, but sibling names imply different use cases (filtering, collection listing). Lacks explicit 'when not to use' guidance.

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

All Lowtoxgear Storefront toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Tools are largely distinct: filter_by_certification is for certification-specific searches, search_products for general keyword search, get_product for single product details, list_collections for collections, and get_policies for policies. The two search tools have overlapping purposes but descriptions clarify their specific intents.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: filter_by_certification, get_policies, get_product, list_collections, search_products. This makes it easy for an agent to predict naming conventions.

Tool Count5/5

With 5 tools covering search, filter, detailed info, collections, and policies, the set is well-scoped for a storefront read-only API. Each tool serves a distinct purpose without unnecessary bloat.

Completeness3/5

The tool set covers key product discovery and policy retrieval, but lacks a dedicated tool to list all products or products by collection. This forces reliance on search_products, which may not return all results or handle empty queries gracefully.

Resources