Skip to main content
Glama

Search products

search_products
Read-only

Search the pharmacy catalog by product name, brand, active ingredient or symptom keyword (for example: paracetamol, sunscreen, Panadol). Returns matching products with price and availability.

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
limitNo
queryYes
currencyNoAlso show prices in this currency (USD, EUR, GBP, RUB); approximate, at today's rate. Payment is in EGP. Default EGP only.
languageNoLanguage of the answer: en, ar, ru, it or de. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / currency
      Added value: +{
      +  "description": "Also show prices in this currency (USD, EUR, GBP, RUB); approximate, at today's rate. Payment is in EGP. Default EGP only.",
      +  "enum": [
      +    "USD",
      +    "EUR",
      +    "EGP",
      +    "RUB",
      +    "GBP"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results carry price and availability, which is useful return context, but says nothing about result ordering, result count, or the maximum of 20 implied by the limit parameter.

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 sentences, no filler, with the searchable attributes front-loaded and the return shape summarized last. Every clause carries information an agent can act on.

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 read-only lookup with a compact four-parameter schema and no output schema, the definition covers what the tool does and roughly what it returns (price, availability). The remaining gap is result-set behavior — paging, ordering, and how 'limit' interacts with the search — which an agent would need in practice.

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 only 50%, and the description compensates for the most important gap by explaining exactly what the required 'query' string accepts — product name, brand, active ingredient, or symptom keyword — which the schema alone ('string, 2-80 chars') does not convey. It still says nothing about 'limit', leaving one parameter undocumented in both places.

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 pharmacy catalog') and enumerates the searchable attributes (name, brand, active ingredient, symptom keyword) with concrete examples. An agent can tell this is a keyword search, but the description never distinguishes it from siblings like get_product or browse_category, so the boundary is inferred rather than stated.

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 implied through the examples (paracetamol, sunscreen, Panadol) which signal 'loose keyword lookup', but there is no explicit guidance on when to prefer this over browse_category or get_product, nor any stated exclusions or prerequisites.

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