Skip to main content
Glama

Get one deal

get_promotion
Read-onlyIdempotent

Full details of one promotion by its id (from a search result): dates, conditions, outlets, source link, and links to add it to a calendar or save it with a start reminder. Pass lat/lng to sort outlets nearest first and get nearest_outlet.

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": {
      "id": "<id>"
    },
    "name": "get_promotion"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe deal's id, from a search or list result.
latNoOptional: where the person is, to find the nearest outlet.
lngNoOptional: longitude, used together with lat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"The deal's id, from a search or list result."
    • addedInput schema / properties / lng / description
      Added value: +"Optional: longitude, used together with lat."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real behavioral context beyond them: what the response contains and the side effect that coordinates reorder outlets nearest-first and inject a nearest_outlet field. It does not cover failure behavior for an unknown id.

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?

A single front-loaded sentence that gives purpose first, then payload, then the optional coordinate behavior. Dense but every clause carries information; it reads as one long run-on rather than being broken into scannable parts.

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?

With no output schema, the description usefully enumerates the returned fields and explains the coordinate-driven output change, which is exactly what an agent needs to decide whether to fetch and how to read the result. Minor gaps remain around error handling for a bad id and whether outlet lists are bounded.

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 100%, so baseline is 3, but the description adds meaning the schema lacks: lat/lng don't just "find the nearest outlet," they sort the outlets array nearest-first and add a nearest_outlet field to the response. The required id's provenance is also restated usefully.

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?

The description states a specific verb and resource (retrieve full details of one promotion by id) and pins down the scope as a single record sourced from a search result, which separates it from list/search siblings like get_deal_list and search_promotions. It also previews the payload (dates, conditions, outlets, source link, calendar links).

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?

"by its id (from a search result)" tells the agent where the required id comes from and thus when this tool is the right next step after a search. It also gives conditional guidance for passing lat/lng. It stops short of naming an explicit alternative or stating when not to call it.

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