Skip to main content
Glama

Quick Liquidity Gap

bpj_quick_liquidity_gap
Read-onlyIdempotent

Compare cash, marketable securities and receivables with current liabilities and quantify the uncovered balance.

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": {
      "cash": "<cash>",
      "securities": "<securities>",
      "receivables": "<receivables>",
      "liabilities": "<liabilities>"
    },
    "name": "bpj_quick_liquidity_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
cashYes
securitiesYes
liabilitiesYes
receivablesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered without description help. The description adds that the operation computes an 'uncovered balance', but it doesn't disclose the sign convention, how shortfalls vs surpluses are reported, or what the return value looks like (no output schema exists).

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?

A single, front-loaded sentence with no filler; the computed quantity is stated up front. It is efficient, though the density means the operational details (formula, units) are absent rather than merely compressed.

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 simple four-number arithmetic tool with full annotation coverage and no output schema, the definition is close to sufficient: inputs are identified and the computed result is named. The main missing piece is the exact aggregation logic (presumably cash + securities + receivables minus liabilities) and the units of the returned figure.

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 description coverage is 0%, so the description must carry the meaning burden, and it does map all four parameters to plain-language terms (cash/equivalents, marketable securities, receivables, current liabilities). However it adds nothing about units, currency assumptions, or how the inputs are combined, which the schema alone cannot convey.

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 names a specific verb pair (compare, quantify) and enumerates the exact resources: cash, marketable securities, receivables against current liabilities. It stops short of distinguishing itself from the highly similar sibling bpj_current_liquidity_position, leaving the agent to guess which liquidity view to pick.

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 explicit when-to-use, when-not-to-use, prerequisite, or alternative named. Usage can only be inferred from the stated purpose, and with a sibling like bpj_current_liquidity_position in the catalog, the absence of routing guidance is a real gap.

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.