Skip to main content
Glama

Valeur Intrinsèque

get_valuation_metrics

Year-end valuation multiples for one ticker. Shows every series the API actually has (P/E, P/S, P/FCF, P/OCF, and P/B, PEG, dividend yield, EV/EBITDA when the source publishes them). Not counted in the Score VI quota.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_valuation_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker or company name (e.g. AAPL, LVMH)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It reveals a useful behavioral trait: the set of metrics varies by source and includes each one only 'when the source publishes them.' It also states that calls are not counted against the Score VI quota, which is a budget constraint the agent can use. However, it says nothing about error behavior for an unrecognized ticker or about latency.

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 short sentences, with the core purpose stated first, then the detail about which metrics are returned, then the quota note. The middle sentence is somewhat long, but every clause, including the list of metrics, adds information about what is returned, so none of the wording is unnecessary.

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?

There is no output schema, so the description must explain what is returned, and it does: it names the metrics plus the caveat that availability depends on the source. With one required parameter that the schema fully documents, little else is needed. The remaining gap is that the description never mentions error or empty-result behavior for an invalid symbol.

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?

There is only one parameter, and schema coverage is 100%: the schema explains that 'symbol' accepts either a ticker or a company name and gives examples. The description confirms the single-ticker scope but adds no meaning beyond what the schema already states, so the baseline score of 3 applies.

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 gives a specific verb and resource: it returns year-end valuation multiples for a single ticker, and it enumerates the exact metrics (P/E, P/S, P/FCF, P/OCF, P/B, PEG, dividend yield, EV/EBITDA). That makes it clearly distinct from the sibling tools get_financial_statements and get_intrinsic_value, even though the description never names those siblings directly.

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?

The phrase 'for one ticker' signals single-symbol usage, and the mention of 'Year-end' implies the data is annual. However, the description never explains when to choose this tool over get_financial_statements or get_intrinsic_value, and it never lists a case where this tool is not appropriate. The usage guidance is therefore only implied, not stated explicitly.

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