Skip to main content
Glama

Loyaltie

Maker profile

get_maker
Read-onlyIdempotent

A maker's profile (story, city and state, shipping policy) and its listed products, by maker id or store link. The products are short references (id, title, price, availability, at most one photo) with no link or warnings: call lookup_catalog for links and warnings before showing any product.

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": {
      "maker": "<maker>"
    },
    "name": "get_maker"
  }
}

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.
makerYesThe maker to read: id, with optional context and attribution.
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.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: the product entries are deliberately abbreviated (at most one photo, no link, no warnings) and a second call is required before presenting them — a trait an agent would otherwise not know. It stops short of stating limits on how many products are returned or any pagination 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?

Two sentences, front-loaded with what is returned and how to address the maker, then the caveat about truncated product data and the required follow-up call. Every clause carries information; nothing 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?

With an output schema present, return values needn't be described, and the description covers the read flow plus the mandatory lookup_catalog follow-up for complete product data. It is nearly complete for a 4-parameter, nested-object tool; only the volume/pagination characteristics of the returned product list are unaddressed.

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%, including detailed coverage of the dual-purpose maker.id field and the optional src, meta, context, and agent_id parameters. The description only restates that the lookup works by maker id or store link, adding no meaning about the optional parameters or the intent/agent_id recording semantics that the schema already documents.

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 opens with a specific resource and enumerates its contents (story, city/state, shipping policy) plus the associated products, and states the two addressing modes (maker id or store link). It also distinguishes its product payload from the richer data in lookup_catalog, so an agent can tell what it is getting here versus elsewhere.

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 gives an explicit prescriptive rule: call lookup_catalog for links and warnings before showing any product, which defines the required follow-up flow. What it lacks is a direct comparison to siblings such as get_product or search_catalog (when to read a maker vs. a single product), so usage is clear but not fully exclusionary.

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