sunnyspoints

Transfer Partner Lookup

lookup_transfer_partners

Read-only

Transfer partner map. Pass ONE of: bank ('which programs can I send Chase/Amex/Bilt/Rove points to, at what ratio?'), program ('which banks feed Flying Blue and which airlines can it book?'), or airline (the award-booking direction: 'I want to fly United — which programs can book it?'). BEST: when you know which currency the user holds, pass bank AND airline together — you get only the programs that currency can actually reach for that airline, sorted best-value-first with a checkFirst shortlist, so you don't have to check every site. Includes alliances and per-program point valuations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lookup_transfer_partners"
  }
}

Input Schema

Name	Required	Description	Default
`bank`	No
`airline`	No
`program`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations only include readOnlyHint=true, which the description complements by revealing behavioral traits such as results sorted best-value-first, inclusion of a checkFirst shortlist, and per-program point valuations. No contradictions, and this context 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?

Three dense sentences pack in purpose, parameter guidance, best-practice tip, and output insights without fluff. Front-loaded with 'Transfer partner map' and structured logically from single-parameter usage to combined mode.

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 lookup tool with optional parameters and no output schema, the description covers input semantics, usage combinations, output ordering, shortlist behavior, and included data (alliances, valuations). It is fully sufficient for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

Schema coverage is 0%, but the description compensates fully by explaining the meaning and purpose of each parameter (bank, program, airline) with illustrative examples. It also describes the combined usage semantics, which is essential given there are no schema descriptions.

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 clearly states it's a 'transfer partner map' and explains the resource and operation with specific examples for each parameter. It distinguishes itself from siblings by focusing on transfer partner connections, which no other sibling tool covers.

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 tells when to pass each single parameter and describes the BEST combined mode (bank+airline) with a rationale. It gives concrete usage examples like 'which programs can I send Chase/Amex...' and 'which banks feed Flying Blue', making alternatives clear without needing to mention not-this-tool.

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

All sunnyspoints tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?