Skip to main content
Glama

Stratalize Intelligence

Get Corporate Debt Benchmark

get_corporate_debt_benchmark
Read-only

Use when assessing a company debt capacity, benchmarking leverage against sector peers, or preparing a refinancing or credit rating discussion. Corporate leverage and debt benchmarks — Net Debt/EBITDA, interest coverage, and debt maturity profiles by credit rating tier and industry. Source: S&P Capital IQ public aggregates and Damodaran. Used by CFOs and treasurers for refinancing, covenant setting, and credit rating management. $0.02 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": {
      "industry": "<industry>"
    },
    "name": "get_corporate_debt_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryYes
credit_rating_tierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds value annotations do not: data provenance ('S&P Capital IQ public aggregates and Damodaran') and a per-call price ('$0.02 USDC per call'), which lets the agent weigh cost and sourcing. It stops short of describing the granularity or shape of what comes back (e.g., one row per rating tier, how many sectors).

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?

Three sentences with the use-case front-loaded and the metric/resource definition second, which is the right order for an agent scanning for a match. The closing sentence ('Used by CFOs and treasurers for refinancing, covenant setting, and credit rating management') largely restates the first sentence's scenarios and is the weakest use of words here.

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 two-parameter, read-only benchmark lookup with no output schema, the definition supplies the metrics covered, the segmentation axes, the upstream sources, and the price — enough for an agent to decide and invoke. The remaining gap is return-shape detail, which matters slightly more here because no output schema exists.

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% with two enum-only parameters, so the description carries the burden. 'By credit rating tier and industry' correctly reveals that both parameters are segmentation dimensions, but it does not explain the enum values (what separates 'b' from 'ccc_and_below'), does not say that credit_rating_tier is optional and what the default aggregate is, and does not clarify that industry is required.

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 concrete resource and scope: 'Corporate leverage and debt benchmarks — Net Debt/EBITDA, interest coverage, and debt maturity profiles by credit rating tier and industry.' The metric list and the 'Corporate' qualifier implicitly separate it from the CRE and real-estate debt siblings, but no sibling is ever named, so differentiation is inferred rather than stated.

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?

Opens with explicit trigger conditions: 'Use when assessing a company debt capacity, benchmarking leverage against sector peers, or preparing a refinancing or credit rating discussion.' That is a clear use-context, but there are no exclusions or named alternatives telling the agent when a different benchmark tool is the better pick.

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