Skip to main content
Glama

Sam's Club MCP

by io.github.mcp-dir

openfinance_provider_status

Read-onlyIdempotent

Checks the LIVE operational status of the Open Finance provider (its public status page) — this is the PROVIDER's health, separate from your own connection's openfinance_get_item_status. Use it whenever data looks incomplete or stale even though a connection shows UPDATED (accounts/transactions/balances missing, a bank not returning everything): it reveals an upstream outage or a known incident on a specific bank/connector, so you can tell a provider-side problem apart from a connection that just needs reconnecting. Returns the global indicator (none/minor/major/critical), degraded components, open incidents, and — when you have banks connected — flags the incidents that affect YOUR connected banks in your_banks_affected.

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context by explaining it checks a public status page (no mutation) and lists the data returned (global indicator, degraded components, etc.), which is useful 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is slightly long but well-structured and front-loaded with the core purpose. Every sentence adds value—no waste. It could be marginally shorter but remains effective.

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 tool with no parameters and no output schema, the description is remarkably complete: it explains the tool's purpose, usage scenario, differentiation from siblings, and what the response will contain. No gaps.

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?

No parameters exist, and schema coverage is 100%. According to guidelines, baseline is 4 for 0-param tools. The description does not need to add parameter info.

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 checks the LIVE operational status of the Open Finance provider via its public status page. It explicitly distinguishes from the sibling tool `openfinance_get_item_status` by specifying it checks provider health, not user connections.

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?

The description provides explicit when-to-use guidance: 'Use it whenever data looks incomplete or stale even though a connection shows UPDATED...'. It also contrasts with the sibling `openfinance_get_item_status` to avoid confusion.

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