Skip to main content
Glama

Current deals

current_deals
Read-only

Products on offer right now, with the discount.

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": "current_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
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

B3/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, non-destructive, closed-world operation. The description adds that results include the discount, but it does not explain what "current" means, how results are ordered, or any pagination behavior.

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?

The description is a single front-loaded sentence with no filler. Its brevity is effective, though it is close to under-specification rather than ideal conciseness.

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

Completeness3/5

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

For a simple read-only list tool, the description covers the core result: current products and discounts. However, with no output schema, it could say more about returned fields and defaults, and it omits any usage guidance relative to sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning for the three parameters: limit, currency, and language. The schema covers currency and language reasonably well, but limit has no schema description and the definition does not compensate for that gap.

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 clearly states the resource and scope: products currently on offer, including their discount. It is understandable without opening the schema, but it lacks an explicit verb and does not distinguish itself from siblings such as search_products or browse_category.

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

Usage Guidelines2/5

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

It gives no explicit guidance on when to use this tool versus alternatives like search_products or browse_category. The phrase "right now" implies a current-deals use case, but no when-not or alternative-selection guidance is provided.

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