Skip to main content
Glama

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

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so this dimension needs added context — and the description delivers two real behavioral facts: per-section graceful degradation on source_unavailable, and a $3.00 USDC per-call charge. It does not state latency, rate limits, or result shape, which keeps it below the top mark for a multi-source fan-in call.

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?

Three tight sentences: trigger first, mechanics and degradation second, pricing last. No filler, no restated title, and the most decision-relevant content (when to use it) is front-loaded.

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 5-parameter read-only aggregator with no output schema, the definition covers trigger context, aggregation scope, partial-failure behavior, and cost — enough to decide and invoke. The remaining gap is return shape: it names the sections fanned in but not what a response looks like when a section degrades, which matters precisely because no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it largely restates the schema: it lists sector as required and the four optional inputs, which the schema's 'required' array and enums already convey. No explanation of how sector/industry steer benchmark selection, or what tier values like 'all' versus 'ig' or 'unrated' actually do to the output. Grouping the params into classification versus credit versus ESG inputs is the only added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-and-resource combination (assessing financial health and deal-readiness) and enumerates the composite sections it aggregates: earnings quality, working capital, WACC, corporate debt, credit spread, ESG. The 'fans in' wording implicitly distinguishes it from the granular single-benchmark siblings (e.g. get_cac_benchmark, get_asc_benchmark) as an aggregator rather than a point lookup.

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?

'Use when assessing financial health and deal-readiness for M&A, lending, or investment committee review' gives concrete trigger contexts, which is stronger than most. It stops short of any exclusion or explicit alternative (e.g. when to call the individual benchmark tools instead of this composite), so it is clear context rather than full when/when-not routing.

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