Skip to main content
Glama

x402-sustainable-growth

Sustainable Growth: Computes sustainable growth rate as ROE times one minus the dividend payout ratio 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-sustainable-growth"
  }
}

Input Schema

NameRequiredDescriptionDefault
roeNo
dividendsNo
netIncomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / dividends / description
      Removed value: -"Dividends to process"
    • removedInput schema / properties / netIncome / description
      Removed value: -"NetIncome to process"
    • removedInput schema / properties / roe / description
      Removed value: -"Roe to process"
  2. Changed3 schema fields changed
    • addedInput schema / properties / dividends
      Added value: +{
      +  "description": "Dividends to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / netIncome
      Added value: +{
      +  "description": "NetIncome to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / roe
      Added value: +{
      +  "description": "Roe to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the payment model (free trial calls per signed wallet), which is genuinely useful context for a paid x402 tool, but says nothing about input format expectations, whether values are decimals or percentages, or what happens on invalid input.

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?

A single front-loaded sentence delivers the tool's purpose and formula with no filler; the trailing emoji/trial note is minor promotional noise rather than structural bloat.

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

Completeness2/5

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

For a 3-parameter computation tool with no annotations, no output schema, and zero schema descriptions, the definition should explain input units/format and the relationship between dividends, netIncome, and payout ratio. It omits all of that, leaving an agent likely to pass wrong-scale values.

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 coverage is 0% and the description only alludes to ROE and dividend payout ratio. The third parameter, netIncome, is never mentioned, and there is no indication that all values are strings, what units are expected, or that NPV of payout ratio must be derived from netIncome and dividends.

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 ('Computes') and resource ('sustainable growth rate') and even gives the formula (ROE × (1 − payout ratio)), so an agent knows precisely what is calculated. It does not distinguish itself from neighboring finance calculators such as x402-retention-ratio or x402-dividend-payout-ratio, which cost it the top mark.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the many finance siblings, no prerequisites, and no note that all three inputs are needed despite none being required. The only extra guidance is promotional ('5 free trial calls per signed wallet').

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