Skip to main content
Glama
Sign In
AwardWallet MCP

AwardWallet MCP

by bbarabe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get loyalty account

get_loyalty_account
Read-onlyIdempotent

Retrieve a single loyalty account by ID to view its balance, elite status, sub-accounts, update links, and paginated transaction history.

Instructions

Returns one loyalty account in full: balance, every tracked property (elite status, account number, points to next level, ...), sub-accounts such as individual cards, links to update it on AwardWallet, and its transaction history, paginated.

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": {
      "accountId": "<accountId>"
    },
    "name": "get_loyalty_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesaccountId from list_loyalty_accounts
historyLimitNoMaximum history rows to return (0 for none)
historyOffsetNoHistory rows to skip, for paging through long histories

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds real value beyond them: it discloses that the response includes full tracked properties, sub-accounts, an AwardWallet update link, and paginated transaction history, which tells the agent the payload is broad and history is paged.

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?

A single dense sentence, front-loaded with the core action and result before the field enumeration. The trailing ellipsis makes the field list slightly open-ended, but there is no wasted text.

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 carries the return-value burden and does list the main response components and pagination. It is nearly complete for a read tool whose annotations already cover safety, though exact paging semantics and any error/permission behavior are unstated.

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 accountId, historyLimit and historyOffset are already documented in the schema. The description mentions pagination but adds no parameter-level detail (units, paging interaction) beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb ('Returns one loyalty account') and enumerates the payload contents (balance, tracked properties, sub-accounts, transaction history), which clearly separates it from the list_loyalty_accounts sibling by emphasizing a single account. It never names the sibling, so it falls just short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no alternatives named. The only routing hint ('accountId from list_loyalty_accounts') lives in the schema, not the description, so the agent gets no usage context from the text itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools