Skip to main content
Glama

get_prepared_offer_terms

Read immutable public purchase-decision terms for an exact prepared offer, including after unpublication. Seller declarations are not verified; references are not fetched. No signature or payment is created.

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

Input Schema

NameRequiredDescriptionDefault
offerIdYes
merchantIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it declares the data immutable and public, states that terms remain readable after unpublication, warns that seller declarations are unverified and references unfetched, and confirms no signature or payment is created. That is a substantive side-effect and trust-boundary disclosure, missing only auth/error behavior.

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?

Three tight sentences, all front-loaded with the core read semantics first and the caveats after. Every clause adds information: scope, availability window, verification limits, and absence of side effects; nothing is filler.

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 read tool with no output schema and no annotations, the description covers purpose and trust caveats well, but leaves the caller unaware of what the returned terms actually contain or how the two required identifiers interact. Adequate, with a visible gap around return shape and identifier semantics.

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?

Schema description coverage is 0% and both parameters (merchantId, offerId) are undocumented UUIDs. The description only obliquely touches the offer parameter via "an exact prepared offer" and says nothing about merchantId or why both are required together, so it does not compensate for the coverage 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?

States a specific verb ("Read") and a precisely bounded resource: immutable public purchase-decision terms for an exact prepared offer. It distinguishes itself from the mutation-oriented siblings (buy_prepared_artifact, complete_prepared_artifact_transfer) by making clear this is a read of terms, though it never names an alternative tool.

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 rather than prescribed: the agent can infer this is the read path for inspecting an offer's published terms, and "including after unpublication" clarifies one important edge case. There is no explicit when-to-use versus when-not, and no statement of prerequisites such as whether a merchant session is needed.

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