Skip to main content
Glama

Get Liquidity Runway

get_liquidity_runway
Read-onlyIdempotent

Estimate a company's mechanical liquidity runway from its latest SEC-tagged cash/current investments and trailing-twelve-month operating cash flow. This is a screening calculation, not management guidance, and excludes future financing, commitments, restricted access, working-capital timing, and forecast changes.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "MRNA"
    },
    "name": "get_liquidity_runway"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesTicker, company name, or CIK.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description goes beyond that by disclosing the calculation method and enumerating five categories of real-world factors the estimate ignores (future financing, commitments, restricted access, working-capital timing, forecast changes) — exactly the interpretive context an agent needs to not over-trust the output. It stops short of stating return units or any freshness/rate-limit behavior.

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?

Two sentences, zero filler, and the core computation is front-loaded before the caveats. Every clause (mechanical, latest SEC-tagged, TTM) earns its place by constraining the estimate's meaning.

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 is the only place an agent could learn the return shape, and it never says whether the runway is expressed in months, years, or a qualitative bucket — a meaningful gap for a numeric estimator. Inputs and caveats are thoroughly covered, so the shortfall is narrow but real.

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?

There is a single parameter with 100% schema description coverage ('Ticker, company name, or CIK'), so the schema already carries its meaning. The description adds nothing about the accepted identifier forms or resolution behavior, which is the baseline 3 for a schema-covered parameter.

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?

States a specific verb-and-resource pair ('estimate a company's mechanical liquidity runway') and even names the underlying inputs (latest SEC-tagged cash/current investments plus TTM operating cash flow). That is far more precise than a tautology, but it never names or contrasts a sibling such as get_company_financials, so an agent must infer that this is a derived screening metric rather than raw financial data.

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 'screening calculation, not management guidance' clause implicitly frames when the number is appropriate, and the exclusion list hints at when it will mislead. However, there is no explicit when-to-use/when-not-to-use routing and no alternative tool is referenced, so the guidance remains implied rather than stated.

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.