Skip to main content
Glama

discover_merchant_offers

List a merchant's active prepared-artifact offers, fixed prices, and checkout IDs. This is public and does not require a bearer key.

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>"
    },
    "name": "discover_merchant_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
merchantIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose one genuinely useful trait: the endpoint is public and requires no bearer key. The word 'active' also signals a filtering behavior. It stops short of covering pagination, empty-result behavior for an unknown merchant, or error semantics for an invalid or inactive merchant ID.

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 short sentences, front-loaded with the verb and resource, then the auth caveat. Every clause carries information; nothing is redundant or belabored.

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 single-parameter, read-only listing with no output schema, the description conveys enough: what is returned (offers, fixed prices, checkout IDs), the scope (active only), and the auth posture. The remaining gap is failure-mode behavior for unknown merchant IDs, which is minor for this tool's complexity.

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?

There is a single required merchantId with 0% schema description coverage, so the schema offers only format and pattern, not meaning. The description's possessive 'a merchant's ... offers' makes clear the parameter selects the merchant whose offers are listed, which is the minimum needed to call it correctly, but it adds no detail on the UUID format or invalid-ID handling — hence 3 rather than 4.

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 ('List a merchant's active prepared-artifact offers, fixed prices, and checkout IDs'), which tells an agent exactly what comes back. It does not explicitly distinguish itself from the sibling resolve_latest_merchant_offer, so it falls short of full sibling differentiation, but the purpose itself is unambiguous.

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 — an agent can infer this is the discovery step before buy_prepared_artifact or resolve_latest_merchant_offer — and the 'public, no bearer key' note sets useful context. However, there is no explicit statement of when to choose this over the offer-resolution sibling, nor any exclusions or prerequisites beyond the auth note.

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