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

Name	Required	Description	Default
`symbol`	Yes	Stock ticker (e.g. AAPL)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026
- changedInput schema / properties / symbol / description
```
Previous value: -"Ticker boursier (ex: AAPL)"New value: +"Stock ticker (e.g. AAPL)"
```
First observedOct 15, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that coverage is source-dependent ('when the source publishes them'), which is useful, but it omits return format, units, null-handling for missing series, period basis, and any read-only/auth context. For a data-retrieval tool with zero annotation support this is thin.

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 two value-bearing sentences are front-loaded and efficient, but the final sentence 'Not counted in the Score VI quota' is internal scoring metadata that is irrelevant to an agent trying to invoke the tool. That non-earning sentence drags down an otherwise tight definition.

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

Completeness3/5

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

With no output schema, the description should carry more of the return-shape burden; it names the metrics but not their units, period basis, or how missing series appear. The source-dependent coverage caveat is a genuinely valuable addition. It is adequate but leaves real gaps for a data-retrieval tool.

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% with a single, well-described 'symbol' parameter, so the schema already does the work and the baseline applies. The description adds the 'one ticker per call' constraint, reinforcing that the symbol is singular and no batch input is accepted. No syntax or format detail beyond the schema is needed.

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 and resource: valuation multiples for a ticker. The second sentence enumerates the exact ratios returned, which makes the output concrete and distinguishes it from siblings like get_intrinsic_value and get_financial_statements. It does not explicitly name an alternative tool, so it falls short of a 5.

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?

Usage is implied by the 'one ticker' scoping and the ratio enumeration, but there is no explicit when-to-use vs. when-not guidance and no named alternative such as get_intrinsic_value for a single fair-value figure. The trailing 'Not counted in the Score VI quota' note is internal metadata, not guidance.

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

All Valeur Intrinsèque tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?