Skip to main content
Glama

optimize_loyalty_portfolio

Read-only

Analyze your loyalty portfolio to surface expiring points, best transfer opportunities, and largest balances, helping you take the right actions.

Instructions

Analyze the user's whole loyalty portfolio and surface the highest-value actions.

Trip-independent. Looks across every loyalty program the user holds — plus the transferable
card currencies (Amex, Chase, Bilt, etc.) that can feed hotel programs — and reports points
expiring soon (ranked by value at risk), the best transfer opportunities, and the largest
balances. When the user's travel profile is available, it also tailors the view to their home
airport, the airlines they fly, their frequent destinations, and when they travel (e.g.
flagging points that expire before their usual travel months). Takes no arguments.

Use this when the user asks how to make the most of their points, what's expiring, or where
they can transfer. For deciding where to book a specific trip, use search_hotels /
compare_rates instead.

Returns:
    A Markdown portfolio summary, or instructions to connect accounts when none are linked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable context: trip-independent, looks across all programs, reports expiring points, transfer opps, tailors to travel profile. Does not contradict annotations.

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?

Description is informative and well-structured, front-loaded with the main verb and resource. A few sentences could be tightened but no wasted words.

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?

Covers all aspects: behavior, when to use, no arguments, return format (Markdown portfolio summary or instructions to connect accounts). With an output schema existing, no further detail on return needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has zero parameters (schema coverage 100%), so baseline is 4. The description explicitly states 'Takes no arguments', which is clear beyond the schema.

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 uses specific verbs ('analyze', 'surface') and resource ('loyalty portfolio') and clearly distinguishes from siblings by mentioning alternatives for trip-specific booking.

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

Usage Guidelines5/5

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

Explicitly states when to use ('how to make the most of points, expiring, transfers') and when not to use (specific trips, pointing to search_hotels/compare_rates).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gondola-ai/gondola-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server