Skip to main content
Glama
JosueM1109

personal-finance-mcp

Get Institutions Status

get_institutions_status
Read-only

Retrieves the current health status of all linked financial institutions, indicating any errors or issues.

Instructions

Return health status for every linked Item/institution.

No additional network calls beyond what all_items already makes (it uses the 5-minute health cache). Enumerates linked Items and reports their current health status.

Returns: {"items": [{"env_key", "institution", "institution_id", "status", "reason"}, ...]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation function that iterates over all linked items via all_items() and returns their health status including env_key, institution name, institution_id, status, and reason.
    def _get_institutions_status_impl() -> dict:
        """Return health status for every linked Item/institution.
    
        No additional network calls beyond what ``all_items`` already makes (it
        uses the 5-minute health cache). Enumerates linked Items and reports their
        current health status.
    
        Returns:
            {"items": [{"env_key", "institution", "institution_id", "status", "reason"}, ...]}
        """
        api = build_api()
        items_out: list[dict] = []
        for env_key, token, health in all_items(api):
            items_out.append({
                "env_key": env_key,
                "institution": health.institution_name or env_key,
                "institution_id": health.institution_id,
                "status": health.status,
                "reason": health.reason,
            })
        return {"items": items_out}
  • server.py:475-478 (registration)
    Registers the 'get_institutions_status' tool on the MCP server with a read-only hint and display title.
    get_institutions_status = mcp.tool(
        annotations={"readOnlyHint": True, "title": "Get Institutions Status"},
        name="get_institutions_status",
    )(_get_institutions_status_impl)
  • Test for the get_institutions_status tool, verifying it returns correct health status for all linked items.
    def test_get_institutions_status_reports_all_items(fake_env_tokens):
        fake_api = MagicMock()
        items = [
            ("CHASE", SecretStr("t1"), ItemHealth("CHASE", "healthy", "ins_3", "Chase")),
            ("FIDELITY", SecretStr("t2"), ItemHealth("FIDELITY", "re_auth_required", "ins_9", "Fidelity", reason="ITEM_LOGIN_REQUIRED")),
        ]
        with patch.object(srv, "build_api", return_value=fake_api), \
             patch.object(srv, "all_items", return_value=items):
            out = srv._get_institutions_status_impl()
        assert len(out["items"]) == 2
        keys = {i["env_key"] for i in out["items"]}
        assert keys == {"CHASE", "FIDELITY"}
        chase = next(i for i in out["items"] if i["env_key"] == "CHASE")
        fid = next(i for i in out["items"] if i["env_key"] == "FIDELITY")
        assert chase["status"] == "healthy"
        assert chase["institution"] == "Chase"
        assert fid["status"] == "re_auth_required"
        assert fid["reason"] == "ITEM_LOGIN_REQUIRED"
Behavior4/5

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

Annotations already declare readOnlyHint=true, confirming safety. The description adds valuable behavioral context: uses a 5-minute health cache and makes no extra network calls, which helps agents understand cost and freshness.

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?

Description is extremely concise: two short paragraphs, no fluff, front-loaded with purpose. Every sentence adds value.

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?

Given no parameters, an output schema exists, and the description includes a return format example with all fields, it is fully sufficient. The caching behavior is also noted, making it complete.

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?

Input schema has zero parameters, so schema coverage is 100%. Description does not need to explain parameters; the only relevant detail is the cached nature, which is already mentioned elsewhere.

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?

Description clearly states 'Return health status for every linked Item/institution.' The verb 'return' and resource are precise, and it distinguishes from sibling tools that deal with financial data like balances or transactions.

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?

Description provides clear context: 'No additional network calls beyond what all_items already makes (it uses the 5-minute health cache).' This implies when to use it (when you need health status cheaply) but lacks explicit when-not or alternative recommendations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JosueM1109/personal-finance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server