Valeur Intrinsèque

get_intrinsic_value

Published Score VI for one ticker, read from the public cache (no fresh full analysis). Returns the score out of 100, a short interpretation, price, P/E, whether an eliminatory criterion failed, the calculation date, a citation and a disclaimer. Does not list the ten criteria and does not return a per-share intrinsic value. Use analyze_stock for the criteria. Counts toward the monthly 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_intrinsic_value"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Stock ticker (e.g. AAPL, MSFT, MC.PA)

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, MSFT, MC.PA)"New value: +"Stock ticker (e.g. AAPL, MSFT, MC.PA)"

First observedOct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses cache provenance (no fresh analysis), quota consumption ('counts toward the monthly Score VI quota'), and explicitly lists what is NOT returned (ten criteria, per-share intrinsic value). It doesn't mention auth requirements or cache staleness/refresh behavior, which keeps it from 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.

Conciseness5/5

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

Four tight sentences: identity/scope first, return contents second, negative scope third, routing and cost last. Every sentence carries distinct information with no repetition of the name or title.

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

Completeness5/5

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

No output schema exists, so the description must describe returns — and it enumerates them (score out of 100, interpretation, price, P/E, eliminatory-criterion flag, calculation date, citation, disclaimer). Combined with the quota note and sibling routing, an agent has everything needed to call it correctly.

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?

Only one parameter, and schema description coverage is 100% with a ticker example already in the schema. The description adds no format or constraint detail beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get/read), resource (published Score VI), and scope (one ticker, from public cache). It explicitly contrasts itself with the sibling analyze_stock, so an agent can distinguish the two without inspecting either schema.

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?

Gives clear selection context: this is the cached/published read ('no fresh full analysis') and it names analyze_stock as the alternative for criteria detail. It stops short of stating when the cache should be preferred over the other valuation siblings (get_valuation_metrics), but the primary routing decision is covered.

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?