Skip to main content
Glama

SwitchWize MCP

Issuer Summary

issuer_summary
Read-onlyIdempotent

Summarize one card issuer's listed cards: how many, how many have no annual fee, the annual fee range, the largest welcome bonus, the longest 0% intro APR, and each card's confirmed terms. Accepts an issuer id or name such as chase or American Express. An unknown issuer returns a structured error with the largest issuers.

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": {
      "issuer": "<issuer>"
    },
    "name": "issuer_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25.
issuerYesIssuer id or name, e.g. chase or American Express.

Output Schema

NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
toolYes
cardsNo
countNo
errorNo
issuerNo
sourceNoWhere the data comes from (URL).
pageUrlNo
issuerIdNo
toolMetaNoVersion and stability of the tool that produced this reply. See /developers#tool-versions.
attributionNo
generatedAtYesISO timestamp this response was computed at.
listedCardsNo
verified_atNo
schemaVersionYes
annualFeeRangeNo
methodologyUrlNo
freshnessStatusNo
longestIntroAprNo
noAnnualFeeCardsNo
largestWelcomeBonusNo
highestHeadlineRewardsRateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered; the description adds real behavioral context beyond them by defining the computed aggregates and by promising a structured error listing the largest issuers when the issuer is unknown. It does not say whether the limit truncates the aggregates themselves or whether the error is thrown versus returned in-band, which keeps it out of the top score.

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?

Three sentences with the purpose and the full metric list front-loaded, followed by input format and failure behavior. The enumeration is dense but every item is meaningful; no filler wording.

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 an output schema present and full schema coverage, the description only needs purpose, aggregate definitions, and edge behavior, all of which it supplies. The remaining gap is pagination/truncation semantics for limit, which matters for a summary tool but is the only notable omission.

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 coverage is 100%, so both parameters are already documented, and the description mostly restates the issuer format ('id or name such as chase or American Express'). It leaves the interaction between limit and the reported counts ambiguous, so it does not add meaning beyond 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?

States a specific verb and resource ('Summarize one card issuer's listed cards') and enumerates exactly what the summary contains: card count, no-annual-fee count, fee range, largest welcome bonus, longest 0% intro APR, and confirmed terms. That enumeration separates it from detail-level siblings like get_card_details or compare_cards, though it never names an alternative.

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

Usage Guidelines4/5

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

The scoping phrase 'one card issuer's' plus the input examples (chase, American Express) make the intended usage clear: issuer-level rollups, not per-card or cross-issuer comparison. There is no explicit when-not guidance or named alternative, but the context is unambiguous.

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.