Skip to main content
Glama

Show a loyalty card

get_card
Read-onlyIdempotent

Shows a saved loyalty card's design and rewards, with an Apple and Google Wallet preview.

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": {
      "card_id": "<card_id>"
    },
    "name": "get_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentNoOptional. One short sentence on what the person asked you to do, e.g. "Set up a stamp card for Ground Up Café". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.
card_idYesCard id from list_cards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / intent
      Added value: +{
      +  "description": "Optional. One short sentence on what the person asked you to do, e.g. \"Set up a stamp card for Ground Up Café\". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restatement. The description adds useful context by disclosing what the call returns (design, rewards, and Wallet preview), which annotations do not cover. It says nothing about authorization requirements or error behavior, so it stays at a solid 3.

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?

A single sentence, front-loaded with the verb and resource, with every clause carrying new information (design, rewards, and Wallet preview). There is no filler, restatement of the title, or trailing caveat to trim.

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 no output schema, the description must describe the return, which it does at a high level by naming the design, rewards, and Wallet preview. The parameter semantics are fully covered by the schema, so the main remaining gaps are the absence of guidance for when to use this tool versus its siblings and details of error behavior; otherwise, it is sufficient for a simple read tool.

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 both parameters (card_id and intent) are fully documented in the schema, and that sets the baseline at 3. The description adds no further meaning about card_id's provenance or the intent field's logging behavior. It neither compensates for nor detracts from the schema.

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 gives a specific verb ('Shows') and resource ('a saved loyalty card'), and it names what the response contains: design, rewards, and an Apple/Google Wallet preview. That detail distinguishes it from list_cards and preview_card_designs without needing to open a schema. However, it does not compare itself to those sibling tools explicitly, so a 4 rather than a 5.

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?

The use case (fetching a single saved card's details) is implied by 'saved loyalty card's design and rewards' plus the required card_id. However, the description states no explicit when-to-use or when-not-to-use guidance, and it does not direct the agent to list_cards for discovery or to preview_card_designs for unsaved designs. The guidance is implicit rather than stated.

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