Skip to main content
Glama

Loyal Spark Holder

Lookup Gift Certificate

lookup_gift_certificate
Read-onlyIdempotent

Preview a gift certificate by LOYAL-XXXXXX code without claiming (face value, expiry, program).

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": {
      "code": "<code>"
    },
    "name": "lookup_gift_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesGift certificate code (LOYAL-XXXX-XXXX).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, and the description adds meaningful context on top: it previews without consuming the certificate and names what is returned (face value, expiry, program). It stops short of describing behavior for invalid, expired, or already-claimed codes, which would be the natural next detail.

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?

One sentence, front-loaded with the verb and resource, with the return fields parenthesized at the end. No redundant wording.

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, annotated read-only tool with no output schema, the description is close to sufficient: it covers purpose, the non-mutating behavior, and the shape of the result. Only the outcome for invalid or claimed codes is left unspecified.

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 coverage is 100% and the single parameter is already documented in the schema, so the description can only reinforce it. It does restate the code parameter but with a slightly different pattern (LOYAL-XXXXXX vs the schema's LOYAL-XXXX-XXXX), adding no new semantics and a small format inconsistency.

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 verb ('Preview'), a specific resource ('a gift certificate'), the lookup key ('LOYAL-XXXXXX code'), and explicitly states the non-claiming scope. Saying 'without claiming' separates it from the sibling claim_gift_certificate, so an agent can select it without opening another schema.

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?

'without claiming' implies the intended case (inspect before redeeming) but never states it as guidance, and there is no mention of when to prefer list_my_gift_certificates or what preconditions exist (e.g. whether an already-claimed code still resolves). Usage 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