Skip to main content
Glama

resolve_latest_merchant_offer

Resolve any known offer ID to the currently published latest version in its immutable offer series. Does not require a bearer key or payment.

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": {
      "merchantId": "<merchantId>",
      "offerId": "<offerId>"
    },
    "name": "resolve_latest_merchant_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerIdYes
merchantIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

It explicitly discloses critical operational behaviors that are not in annotations or schema, specifically that the operation is safe from a payment perspective and does not require a bearer key.

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?

The description is extremely concise, using two efficient sentences to convey the core function, operational limitations, and the nature of the offered data series.

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?

While it addresses authentication and the nature of the data resolution, it is slightly incomplete for a complex ID-based tool. An agent still lacks knowledge of the expected structure or content of the returned resolved offer data.

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 input schema details the UUID format and structure for both parameters. The description adds no semantic meaning to 'merchantId' or 'offerId' beyond stating they are identifiers.

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 tool resolves a known offer ID to its latest published version in an immutable series. This purpose is highly specific and distinguishes it from other related functions like discovery or selection tools.

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?

The description is silent on when to use this tool versus alternatives like 'discover_merchant_offers' or 'select_buyer_request_offer.' It lacks context on whether this is an initial lookup or a step within a workflow.

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