Skip to main content
Glama

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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it discloses the source (public cache, no fresh analysis), the exact payload (score out of 100, interpretation, price, P/E, eliminatory-criterion flag, calculation date, citation, disclaimer), two negative guarantees (no criteria list, no per-share intrinsic value), and a quota cost. That is unusually complete behavioral disclosure.

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?

Front-loaded with purpose and cache provenance, then payload, then negative scope, then cost — a logical ordering with no filler sentences. The middle sentence is a long run-on enumeration of return fields, which is dense but each item is informative.

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?

With no output schema and no annotations, the description must explain both the return shape and the safety profile, and it does: it enumerates returned fields, states what is not returned, and clarifies the cache/read nature. An agent has everything needed to call it and interpret the result 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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The description adds only that it is 'one ticker'; it does not clarify whether company names really resolve or how ambiguity is handled, despite the schema mentioning both tickers and names.

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 and resource ('Published Score VI for one ticker, read from the public cache') and immediately scopes it against the heavier alternative ('no fresh full analysis'). An agent can distinguish this from analyze_stock or get_valuation_metrics without opening a 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?

Explains the selection condition clearly — read the cached published score, and go to analyze_stock if the ten criteria or a full analysis are needed. It also warns that the call consumes monthly quota, which affects when an agent should spend it. It stops short of stating explicit exclusions for the other score siblings (moat, management), which is the only gap.

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