Skip to main content
Glama

Liquidity and Funding

liquidity_funding
Read-onlyIdempotent

Liquid assets, securities and their unrealized gains or losses, loans against deposits, the deposit base (core, uninsured, brokered), borrowings, the cost of funding and capital headroom, by quarter with asset-tier medians. (Source: FFIEC Call Report + UBPR (BankRegReports).) Dollar amounts are in thousands of US dollars ($000s); ratios are percentages.

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": {
      "rssd_id": "<rssd_id>"
    },
    "name": "liquidity_funding"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.
quartersNoQuarters of history, 1 to 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the upstream sources (FFIEC Call Report + UBPR via BankRegReports), the unit convention ($000s for dollars, percentages for ratios), and the presence of asset-tier medians, which tells the agent this result is peer-benchmarked rather than raw. It stops short of describing pagination or per-quarter row structure.

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?

One dense metric-list sentence plus a compact parenthetical for source and units; nothing is padded or redundant. It is not ideally front-loaded, since the reader must parse a long noun list before learning the unit and source conventions, but sizing is appropriate for the breadth of data covered.

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?

For a two-parameter read-only retrieval tool with a fully documented schema, the description supplies the missing pieces an agent needs: domain scope, units, source, and peer-median framing. With no output schema present, a brief note on the return shape (per-quarter rows) would be the only remaining gap.

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 (rssd_id, quarters) are already documented in the schema with examples and a 1–20 range. The description's phrase 'by quarter' loosely reinforces the quarters parameter but adds no new syntax or semantics. Baseline 3 applies where the schema does the heavy lifting.

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?

The description enumerates exactly which metrics the tool surfaces (liquid assets, securities and unrealized gains/losses, loans against deposits, deposit base split into core/uninsured/brokered, borrowings, funding cost, capital headroom) and at what granularity (quarterly, with asset-tier medians). That is a specific resource definition an agent can match to a question. It lacks an explicit verb phrase and does not state how it differs from overlapping siblings like deposits or securities, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated prerequisites, and no routing to alternatives, even though deposits and securities are obvious overlapping siblings. The agent must infer from the metric list alone whether to call this or those. Usage is only implied by subject matter.

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.

Resources