Skip to main content
Glama

Mastering Financial Markets

MFM long-term price calculator (formula v47)

long_term_calculator
Read-onlyIdempotent

Recomputes MFM's long-term part of a price with the premium and the growth chosen by the user, with the same rule and bounds as the calculator of /en/top-down-bottom-up/#formula. Give exactly one of company (MFM company id: its owner earnings; counts as one company page of the account quota, nothing more if that company was already read today) or market (US, EU, JP, CH: the net income of the basket's companies, the published bottom-up route; no quota). erp and x are fractions (0.04 = 4%, 0.01 = 1 point); defaults 4% and 0; out-of-range values are refused. Owner earnings, the payable share q, the return on equity, growth g and the spreads are measured and fixed. The result moves toward the market price but never past it. Optional live comparison: live_price (company: price per share in the price currency; index or ETF: also month_end_price of the same instrument on MFM's price month). The long-term part is dated, not real time. Descriptive only, never advice.

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": "long_term_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoGrowth above the 10-year government bond rate, fraction (default 0; range in the parameter file)
erpNoEquity risk premium chosen by the user, fraction (default 0.04; range in the parameter file)
marketNoIndex or state with a published bottom-up long-term part
companyNoMFM company id, as in /en/company/<id>/ (e.g. aapl)
live_priceNoLive price fetched by the AI itself (optional), same unit and currency as MFM's price
month_end_priceNoIndex or ETF only: close of the same instrument on MFM's price month end, from the same source as live_price

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses quota accounting (company counts as one page, market costs none), refusal of out-of-range inputs, that owner earnings and growth inputs are fixed, that the result is bounded by the market price, and that the output is dated rather than real time. It also states the tool is descriptive, never advice.

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?

The purpose is front-loaded and nearly every clause carries new information. Density is high, with nested parentheticals that slow reading, but there is little filler to remove.

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 six-parameter calculation with no output schema, the definition covers input meaning, the exclusive company/market routes, quota effects, and the nature of the returned value. Minor gaps remain on error behavior and output shape, but nothing critical for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: fractional units with a converted example ('0.01 = 1 point'), defaults of 4% and 0, the unit and currency expectations for live_price, and the month_end_price requirement being restricted to index or ETF instruments.

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 uses a specific verb and resource: 'Recomputes MFM's long-term part of a price with the premium and the growth chosen by the user,' tied to a named formula page. It is clearly a valuation calculation, though it never explicitly distinguishes itself from siblings like bond_calculator or portfolio_calculator.

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?

It gives a hard selection rule — 'Give exactly one of company ... or market' — and explains what each route computes and costs in quota. It also frames live_price as an optional enhancement. No explicit statement of when not to use the tool, so it stops short of a 5.

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