Skip to main content
Glama

Loyaltie

Look up products

lookup_catalog
Read-onlyIdempotent

Full products for 1 to 50 known ids or loyaltie.com product URLs, exactly as other calls returned them. Unknown ids are reported in messages; when none is found the call fails with not_found. Amounts are cents.

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

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 products to read: ids, with optional filters, context and view.
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

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, but the description adds useful operational details: the 1–50 limit, partial-success reporting for unknown ids, not_found when none resolve, and that amounts are in cents. It does not discuss auth or rate limits, though those are less central for this read-only lookup.

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 compact sentences front-load the core scope, then failure behavior, then the unit convention. There is no filler, and every sentence contributes useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and full annotation coverage, the description does not need to explain return shape or safety. It covers the key non-obvious behavior for this nested-schema lookup: known-id scope, 1–50 limit, unknown-id reporting, total-miss failure, and cents.

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 ids, URLs, view, context, and filters. The description reinforces the id count limit and URL form plus cents, but adds little parameter meaning beyond the schema, so baseline 3 is appropriate.

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 gives a specific operation and resource: full product records for 1 to 50 known ids or loyaltie.com product URLs. The 'known ids' constraint implicitly separates this direct lookup from discovery-oriented siblings such as search_catalog, even though it does not name that sibling.

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 states the intended input context clearly: ids or URLs exactly as returned by other calls, plus what happens when some or all ids are unknown. It does not explicitly name search_catalog as the alternative for discovery or provide broader exclusions beyond the known-id requirement.

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