Skip to main content
Glama

PowerBankPortatil Store

Search products

search_products
Read-only

Search the PowerBankPortatil catalog (magnetic MagSafe-compatible power banks and magnetic phone cases). Returns name, price in EUR, stock, slug and URL of each match. All filters are optional; no filter returns the whole catalog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language (default en)
typeNo
colorNoOrange, White, Silver, Gold or Clear
queryNoFree text, e.g. "10000mAh white"
capacityNoBattery capacity in mAh
max_priceNoMaximum price in EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "es",
      -  "fr",
      -  "de"
      -]New value: +[
      +  "en",
      +  "fr",
      +  "es",
      +  "de",
      +  "it",
      +  "pt",
      +  "nl"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes further by enumerating the returned fields (name, price in EUR, stock, slug, URL), which is valuable given there is no output schema. It does not mention catalog size, result limits, or sorting, which is the main remaining behavioral gap for an unfiltered full-catalog query.

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?

Three short sentences, front-loaded with the verb and resource, then return shape, then the optional-filter note. No filler and nothing repeated from structured fields.

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 six-parameter, zero-required search tool with no output schema, the description covers purpose, return fields, and the no-filter behavior. It is only slightly incomplete in not addressing result volume or whether the unfiltered catalog is bounded.

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 83%, so the schema already documents most parameters (lang, color, query, capacity, max_price). The description adds only that filters are optional and that omitting them returns everything; it adds no semantics for lang, type, or color beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the PowerBankPortatil catalog') and scopes the domain to magnetic MagSafe power banks and magnetic cases. It implicitly separates itself from get_product_details by describing summary fields returned, but it never names that sibling or explicitly contrasts the two.

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

Usage Guidelines3/5

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

'All filters are optional; no filter returns the whole catalog' is genuinely useful call guidance, telling the agent it can invoke with zero arguments to enumerate everything. However, there is no explicit when-to-use-this vs when-to-use-get_product_details or check_phone_compatibility guidance, so the routing decision 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources