Skip to main content
Glama

Sam's Club MCP

by io.github.mcp-dir

openfinance_list_connections

Read-onlyIdempotent

Returns the saved bank connections for this install: connector_id, item_id, bank name, a per-connection reconnect_url, and an add_connection_url to link additional banks via the Open Finance widget. The reconnect_url reopens the widget in UPDATE mode for that EXISTING connection (user re-enters credentials / MFA token and the data refreshes in place) — use it when a connection needs re-authentication (MFA connectors, LOGIN_ERROR, stale non-Open-Finance data). It does NOT consume a connection slot and does NOT require disconnecting first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by explaining the update mode behavior of reconnect_url, that it does not consume a slot or require disconnecting, which goes beyond 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?

The description is well-structured and informative, though slightly lengthy. It front-loads the purpose and bulletizes key outputs, making it easy to skim.

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?

Given zero parameters and no output schema, the description adequately explains return values and usage context, leaving little ambiguity for an agent.

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?

There are no parameters, so baseline is 4. No additional parameter information is needed.

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 the tool returns saved bank connections with specific fields (connector_id, item_id, bank name, reconnect_url, add_connection_url), distinguishing it from sibling tools by detailing the output and use cases for reconnect_url.

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 description provides guidance on when to use the reconnect_url (for re-authentication, MFA, LOGIN_ERROR, stale data) and clarifies it does not consume a connection slot. However, it does not explicitly compare to all sibling tools for when to use this list vs others.

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

All Sam's Club MCP 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

A3.9/5.0
Disambiguation4/5

The openfinance_* tools are mostly separated by resource (accounts, bills, loans, investments, connections), and the meta tools are distinct. The main ambiguities are openfinance_list_transactions vs openfinance_list_transactions_by_item, and openfinance_get_credit_card_bill vs openfinance_list_credit_card_bills, though their descriptions do clarify different intents.

Naming Consistency3/5

The openfinance_* family follows a consistent verb_noun pattern, and the generic platform tools use bare lowercase names like connect, authenticate, and marketplace. The mixed prefixes and the occasional singular/plural variation (get_credit_card_bill vs list_credit_card_bills) make the overall namespace readable but not fully uniform.

Tool Count3/5

25 tools is at the heavy end and combines two distinct areas: platform/meta tooling and a deep Open Finance adapter. Most openfinance tools are justifed by real endpoints, but the count feels bulky for an agent to browse, and the marketplace tool packs an unusually large number of capabilities into a single entry.

Completeness4/5

The Open Finance surface is unusually complete: accounts, balances, transactions, credit-card bills, loans, investments, connection status, force sync, provider status, category correction, and disconnect are all present. The platform side is also broad via marketplace and toolkit_info, with only minor granularity gaps such as no dedicated get-single-transaction tool or separate marketplace sub-tools.

Resources