Skip to main content
Glama

Loyaltie

Product details

get_product
Read-onlyIdempotent

One full product by id or URL: price, conditional offers with terms, variants, availability, rating, ships-from, the verbatim Agent Context, and allergen and safety disclosures as warning messages. Skip it when earlier results already answer. An unknown id fails with not_found.

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": {
      "catalog": "<catalog>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
srcNoSend "skill" when you were set up by the Loyaltie Skill; returned links then carry src=skill. Default "api"; any other value counts as "api".
metaNoOptional UCP request metadata. meta["ucp-agent"].profile is your UCP agent profile URL; it is recorded, never required.
catalogYesThe product to read: id, with optional selected, preferences, context and filters.
agent_idNoYour agent id. Every loyaltie.com link returned then carries agent=<agent_id>, so Loyaltie knows which agent helped.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: an unknown id fails with not_found, allergen and safety disclosures arrive as warning messages, and the Agent Context is returned verbatim. It does not mention rate limits or pagination, but for a single-record read that is a minor omission.

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?

Three sentences, front-loaded with the resource and its payload, followed by the skip condition and the error case. The long enumeration of returned fields is dense but each item aids selection; no sentence is filler.

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?

An output schema exists, so return shape need not be explained, yet the description still names the salient payload fields, which helps an agent decide whether to call it. The complex nested filters (price, shops, ships_to, categories) are left entirely to the 100%-covered schema, which is a defensible division of labor. Adding the not_found failure mode rounds out what an agent needs.

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?

Schema description coverage is 100%, so the schema already documents catalog.id, src, meta and agent_id in detail. The description echoes the id-or-URL duality and the 'verbatim Agent Context' return, but adds no syntax or format guidance beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific retrieval ('One full product by id or URL') and enumerates what comes back: price, conditional offers with terms, variants, availability, rating, ships-from, Agent Context, allergen/safety disclosures. That is far more specific than the title 'Product details'. It stops short of naming the sibling it differs from (search_catalog / lookup_catalog), so an agent must infer the boundary from 'earlier results'.

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?

It supplies an explicit exclusion: 'Skip it when earlier results already answer', which tells the agent not to re-fetch data it already has. No alternative tool is named for the case where earlier results do not answer, so the routing is implied rather than spelled out.

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