Leeway Financial Data

ratings

ratings

Read-only

Get Leeway ratings for a listing. Market-Fit measures how well the company fits historically successful fundamental patterns using 18 metrics across profitability, financial strength and valuation; adaptive peer groups learn optimal ranges from roughly four years of returns, hit rates and stability, with rolling recalibration and forecasts. Business-Rating measures long-term business quality independently of price across twelve dimensions; it is produced from scored, fact-checked analysis. Cycle-Rating measures whether the listing is cheap or expensive versus its own valuation history using valuation multiples, leverage and dividend yield; higher means historically cheaper. Leeway-Score combines Market-Fit, Business and Cycle in equal thirds. Market-Fit, Business and Leeway-Score range from -100 to +100; Cycle ranges from 0 to 100. Factor statistics include the current raw value, machine-learning score, average performance, normalized performance, win rate and deviation. These are analytical ratings, not buy recommendations. Methodology: https://leeway.tech/en/hilfe/scores; Market-Fit: https://leeway.tech/en/hilfe/scores/marketfit; Business: https://leeway.tech/en/hilfe/scores/business; Cycle: https://leeway.tech/en/hilfe/scores/cycle. Free access is SAP only; Investor covers US/Europe; Trader worldwide.

Input Schema

Name	Required	Description	Default
`symbolExchange`	Yes	Symbol and exchange. Example: SAP.XETRA

Output Schema

Name	Required	Description	Default
`code`	No
`name`	No
`country`	No
`factors`	No
`ratings`	No
`exchange`	No
`discontinued`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedOutput schema / properties / ratings / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "business": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "cycle": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "earnings": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "esg": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "financial": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "growth": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "leewayScore": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "marketFit": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "marketFitTrend": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "marketFitTrendScore": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "price": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "value": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "business": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "cycle": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "earnings": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "financial": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "growth": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "leewayScore": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "marketFit": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "marketFitTrend": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "marketFitTrendScore": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "price": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "value": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With annotations already declaring readOnly and closed-world, the description goes further by disclosing score ranges (-100..+100, Cycle 0..100), the fact these are analytical not buy recommendations, and entitlement limits per subscription tier — genuinely useful context. It omits error/empty-result behavior, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the body is a dense wall of prose mixing rating definitions, range clamps, factor-statistic field lists, disclaimers, and four methodology URLs. Several sentences (notably the factor-statistics enumeration, duplicated by the output schema) do not earn their place.

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 single-parameter tool whose output schema exists, the description is largely complete: it explains what each of the four scores means, their scales, and access constraints. It over-describes return fields while saying nothing about failure modes, but nothing essential for invoking it 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% and the schema supplies the "SAP.XETRA" example, so the baseline would be 3; the description earns an extra point by tying subscription tier to regional exchange coverage, which informs which symbol/exchange an agent may validly pass.

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 opening sentence states a specific verb and resource ("Get Leeway ratings for a listing") and the following sentences define each rating type, so an agent can tell this returns composite analytical scores rather than raw fundamentals. It never names a sibling, though, so differentiation from tools like fundamentals or ai_company must be inferred.

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

Usage Guidelines3/5

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

There is no explicit when-to-use/when-not statement or named alternative; usage is only implied by the description of what the ratings measure. The access-tier note (SAP-only free, Investor US/Europe, Trader worldwide) is the closest thing to guidance, but it constrains coverage rather than tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Leeway Financial Data tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?