Skip to main content
Glama

Valeur Intrinsèque

analyze_stock

Full fundamental snapshot for one ticker using Valeur Intrinsèque's Score VI. Returns the company profile, the Score VI out of 100 with each scored criterion, and key ratios (EPS, P/E, ROE, debt/equity, dividend yield, current ratio, book value per share, P/B). Prints a per-share intrinsic value and margin of safety only when the API payload already includes one. 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": "analyze_stock"
  }
}

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

A3.8/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 substantial work: it discloses the conditional nature of the intrinsic value and margin of safety fields ('only when the API payload already includes one'), and it warns that the call counts toward the monthly Score VI quota, which is real cost/rate-limit context an agent cannot get elsewhere. Gaps remain on failure behavior for an invalid or ambiguous ticker and on data freshness, so it falls short of 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 sentences, front-loaded with the core purpose and followed by return contents, the conditional caveat, and the quota cost. The ratio list is long but each item is meaningful payload information, and no sentence is redundant.

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?

With no output schema and no annotations, the description must explain return values, and it does so concretely by enumerating the profile, scored criteria, and named ratios, plus flagging the conditional intrinsic value field. It is nearly complete for a one-parameter read tool; only error handling and data recency are unaddressed.

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 required parameter with 100% schema description coverage, including examples (AAPL, LVMH, MC.PA), so the schema already does the heavy lifting. The description adds nothing about ticker format, exchange suffixes, or how company names are resolved when both are accepted. Baseline 3 applies when the schema fully documents the parameter.

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 names a specific verb and resource: a full fundamental snapshot for one ticker built on Valeur Intrinsèque's Score VI, and it enumerates the payload (profile, Score VI with criteria, key ratios). An agent can tell this is a single-company fundamental report rather than a price or comparison call, but it never explicitly distinguishes itself from siblings like get_intrinsic_value, get_valuation_metrics, or get_management_score, which overlap heavily with the listed contents.

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 only implied: the tool is for getting a broad fundamental picture of one ticker. There is no explicit when-to-use/when-not-to-use statement and no named alternative for narrower needs such as price, valuation metrics only, or comparing multiple stocks. The one routing hint is conditional — intrinsic value appears only when the payload already includes it — which suggests get_intrinsic_value for guaranteed coverage, but the agent must infer that.

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