Skip to main content
Glama

Current Liquidity Position

bpj_current_liquidity_position
Read-onlyIdempotent

Calculate working capital and the multiple of short-term obligations covered by current assets.

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": {
      "assets": "<assets>",
      "liabilities": "<liabilities>"
    },
    "name": "bpj_current_liquidity_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsYes
liabilitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile needs no restatement. The description adds that the tool performs a pure computation rather than a lookup, which is useful, but says nothing about precision, rounding, or how results are returned.

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?

A single front-loaded sentence with no filler; both computed quantities are named up front and nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry the return-value burden; it names the two computed metrics but does not say how they are returned (order, format, rounding) or what happens at edge cases. Adequate for a simple two-input calculator, but not fully self-sufficient.

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%, but the parameter titles ("Current assets", "Current liabilities") carry the meaning. The description reinforces this by framing liabilities as "short-term obligations" and assets as current assets, yet it never states units, currency assumptions, or that liabilities must be non-zero (the schema enforces a 0.01 minimum).

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?

A specific verb ("Calculate") plus two precisely named outputs: working capital and the current-asset coverage multiple of short-term obligations. It is clear what the tool computes and how the two inputs are used, though it never explicitly distinguishes itself from nearby liquidity siblings such as bpj_quick_liquidity_gap.

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

Usage Guidelines3/5

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

The name and description imply the usage domain (assessing short-term solvency from balance-sheet figures), giving implied when-to-use context, but there is no explicit guidance on when to prefer this over the quick-liquidity or other liquidity tools, and no stated prerequisites.

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.