Skip to main content
Glama

Stratalize Healthcare

Get Financial Deal Readiness

get_financial_deal_readiness
Read-only

Use when assessing financial health and deal-readiness for M&A, lending, or investment committee review. Fans in earnings quality, working capital, WACC, corporate debt, credit spread, and ESG benchmarks — degrading per-section on source_unavailable. Input sector (required); optional industry, credit_rating_tier, credit_spread_tier, esg_focus. $3.00 USDC per call.

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": {
      "sector": "<sector>"
    },
    "name": "get_financial_deal_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYes
industryNo
esg_focusNo
credit_rating_tierNo
credit_spread_tierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds two genuinely non-obvious behaviors: per-section degradation on source_unavailable (partial results are possible) and a $3.00 USDC per-call cost. It does not say what a degraded response looks like or whether the full price is charged on partial failure, which is the main remaining behavioral gap.

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?

Two dense sentences, front-loaded with the use case, then the fan-in scope, then inputs, then price. No filler. The middle clause is somewhat list-heavy, but every element (sections, degradation, cost) is information the agent needs before calling.

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?

With no output schema, the description usefully enumerates the report sections the caller will receive and discloses both the partial-failure mode and the per-call price — enough to decide and budget. What remains unstated is the response structure (how sections are keyed) and whether results are cached or scoped to a fiscal period.

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% across 5 enum parameters, so the description must carry the semantics. It does name all five and flags sector as required, but adds no meaning beyond the parameter names themselves — for example, it never explains what credit_spread_tier values like 'ig', 'hy', or 'bbb' select, or how industry interacts with sector.

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 the analytical job (financial health and deal-readiness for M&A, lending, or IC review) and enumerates the six component analyses it fans in (earnings quality, working capital, WACC, corporate debt, credit spread, ESG benchmarks). That is far more specific than the title alone, though it never names a sibling tool to contrast against, so an agent must infer the boundary from the section list.

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?

The opening 'Use when assessing financial health and deal-readiness for M&A, lending, or investment committee review' gives a concrete triggering context rather than a generic 'use this to get data'. No exclusion or alternative is stated, so there is no guidance on when a narrower sibling (e.g. a single-benchmark tool) would be preferable.

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