Skip to main content
Glama

sunnyspoints

by io.github.swarnavspujari

Live Deals

list_live_deals
Read-only

List the flight deals currently posted on sunnyspoints.com (route, cash/points pricing, cents-per-point, status). Optionally filter by dealType, cabin, fromAirport, or status. Expired deals are excluded unless status='expired' is requested. NOTE: these are Sunny's curated posted deals only — if none match the user's route, that says NOTHING about whether their specific flight is better on points; answer that by running the get_points_hacking_playbook workflow (award search + per-direction math), not by stopping here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cabinNo
statusNo
dealTypeNo
fromAirportNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Even with readOnlyHint and openWorldHint annotations, the description adds valuable context: deals are curated posted deals only, absence of matches is not meaningful about the user's specific flight, and expired deals are filtered out unless status='expired' is passed. This goes beyond the annotations.

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?

The description is two concise sentences plus a note, front-loaded with the action and resource. Every sentence contributes meaningful information without redundancy.

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?

For a read-only list tool with no required parameters and no output schema, the description covers return fields, filtering options, default behavior, and the critical limitation and fallback workflow. This is complete for the tool's complexity.

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?

The description names all four filter parameters and explains the semantic of the status parameter (expired excluded by default, include with status='expired'). With 0% schema coverage, this adds meaning beyond the schema, though it does not specify value formats for cabin or fromAirport.

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 the specific verb 'List', names the resource 'flight deals currently posted on sunnyspoints.com', and details return fields (route, points/cash pricing, cents-per-point, status). It also distinguishes from siblings by noting these are curated posted deals only and pointing to get_points_hacking_playbook for actual award comparison.

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 not to use this tool and provides an alternative: if no deals match, run the get_points_hacking_playbook workflow instead of stopping. Also clarifies the default exclusion of expired deals unless status='expired' is requested, giving clear contextual guidance.

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

All sunnyspoints toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool serves a distinct purpose: deal browsing (list_live_deals, get_deal), valuation (get_points_values), decision calculators (calculate_points_or_cash, evaluate_signup_bonus), workflow guidance (get_points_hacking_playbook), membership info, transfer partner lookup, and subscription. There's no overlap—get_deal and list_live_deals are complementary (list vs. detail).

Naming Consistency5/5

All tool names follow the same verb_noun pattern with snake_case (e.g., calculate_points_or_cash, get_membership_info, lookup_transfer_partners). The verbs vary but are all action-oriented, and the nouns clearly indicate the resource, resulting in a predictable and consistent naming scheme.

Tool Count5/5

With 9 tools, the server is well-scoped for its purpose—covering deal discovery, detailed evaluations, reference data, workflow guidance, and user subscription. Each tool earns its place without redundancy, and the count is within the ideal range for clarity.

Completeness5/5

The toolset covers the full lifecycle of a points-hacking user: discover deals, get valuations, decide cash vs. points, evaluate sign-up bonuses, transfer partners, follow the playbook, and subscribe for alerts. No critical operations are missing, and the playbook tool orchestrates the workflow to handle gaps like flight search externally.

Resources