Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

search_tools

Read-only

Find WebCake tools by keyword across the full catalog, including capabilities not loaded natively. Returns name, group, description and JSON input schema so you can run the right tool.

Instructions

Find WebCake tools by keyword across the FULL catalog — including capabilities NOT loaded natively (marketing/CRM, translations, media, appointments, affiliate, reviews, domains/SEO/shipping, brands/tags/ribbons, courses, sale channels, automation…). Returns name, group, description and JSON input schema. Then run one with invoke_read_tool (read-only) or invoke_tool.

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_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoRestrict to a group name (see list_tool_groups)
limitNoMax results (default 8)
queryYesKeywords, e.g. 'affiliate payout', 'translate product', 'add domain ssl', 'block phone'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.31.8

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe lookup, and the description adds meaningful behavior beyond it: the result payload shape and the two invocation paths that consume those results. It stops short of disclosing ranking/relevance behavior or what happens when the limit is hit or zero results are returned, which keeps it from a 5.

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?

Two sentences, front-loaded with the core action and followed by the output and next-step information. The long parenthetical catalog enumeration is defensible as evidence of breadth but is slightly dense; trimming it to a few representative examples would tighten the definition without losing signal.

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?

There is no output schema, so the description's explicit statement of return fields is necessary and present, and it also closes the loop on what to do with the results. With 100% parameter coverage in the schema and a readOnly annotation handling the safety profile, nothing material is missing for an agent deciding whether and how to call this.

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%, with per-parameter descriptions for group, limit and query including concrete query examples, so the structured schema carries the load. The description only reinforces the keyword-search concept and adds no syntax or formatting detail beyond what the schema already says — the expected baseline of 3.

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 WebCake tools by keyword across the FULL catalog') and immediately distinguishes itself from the native tool set by scoping to capabilities NOT loaded natively. It also enumerates the return fields (name, group, description, JSON input schema), so the agent knows exactly what it gets back.

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?

It clearly frames the use case (discovering tools that aren't loaded natively) and names the follow-up alternatives — invoke_read_tool for read-only execution and invoke_tool otherwise — which is genuine routing guidance. The only gap is that it never explicitly points to list_tool_groups or says when not to search (e.g., when the capability is already native), leaving some inference to the agent.

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