Skip to main content
Glama

search_products

Search the ProfitDeals (profitdeals.gr, Greece) product catalog. Online store in Greece by GETA Hellas (since 1999): health & beauty, electronics, home & kitchen, security, computer and car accessories, gadgets, toys and gifts. Works in Greek or English. Returns products with current price in EUR, stock status, product page url and image.

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

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, default 1
queryYesWhat the customer is looking for
max_resultsNo1-30, default 10
in_stock_onlyNoOnly products available now

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry behavior alone, and it does disclose the return payload (price in EUR, stock status, product page URL, image) and language handling. It says nothing about result ordering/relevance, behavior on zero results, pagination behavior beyond what the schema states, or any rate limits, which leaves meaningful gaps for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core action and stays to one short paragraph, which is good. But 'by GETA Hellas (since 1999)' and the exhaustive category enumeration consume tokens without changing how an agent invokes the tool, so not every clause 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 four-parameter search tool with fully documented params and no output schema, the description covers catalog scope, language handling, and return fields well. It is only slightly incomplete in not addressing result ordering, pagination expectations, or the empty-result case.

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%, so the baseline is 3. The description adds a small amount beyond the schema by noting that queries can be in Greek or English, which affects how the 'query' parameter should be formed, but it does not touch page, max_results, or in_stock_only semantics.

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?

The description opens with a specific verb and resource: 'Search the ProfitDeals ... product catalog', and names the domain (profitdeals.gr, Greece). It does not, however, distinguish itself from the sibling get_product, which is the natural alternative for retrieving a single product's details, so it stops short of a 5.

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?

Usage is only implied by the verb 'search' and the catalog scope; there is no statement of when to use this versus get_product (e.g., keyword discovery first, then detail lookup) and no exclusions. The note that queries work in Greek or English is a useful usage hint but is the only explicit guidance.

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