Skip to main content
Glama

One-call valuation brief: intrinsic value, margin of safety, verdict, guru holders

brief
Read-only

Call this first when asked whether a listed company looks cheap or expensive, what it is worth, or which well-known investors own it: one call returns the intrinsic value per share (with each valuation method as an input), the owner-earnings value, the margin of safety against the current price, a deterministic verdict sentence about where the price sits against our value range, the top tracked 13F holders and their last move, and the company profile. Every number carries its unit, period, as-of date and a sec.gov source link, and checks lists the sanity checks it passed. A value built from statements filed in another currency and converted to USD carries fx (original currency, rate, rate date) and passes currency_consistent; when the currency is not known the flag currency_unverified says the check did not run. If the valuation fails a check (for example an intrinsic value more than 20x the price, or statements left in a currency other than the USD price), the valuation figures are withheld, withheld is true, checks.failed names the check, and the call is not charged. Input: ticker (path), e.g. GET /brief/KO. The first brief each UTC day is free per key and per keyless address; after that 0.30 credits. Data and analysis, not investment advice. (GET https://app.deepvalues.ai/api/v1/brief/{ticker} — 0.3 credits per call; works with no credentials up to 1 call(s)/day per address)

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": {
      "ticker": "<ticker>"
    },
    "name": "brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesUS listing symbol, e.g. KO or BRK.B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds substantial behavior beyond that: valuation figures are withheld when a sanity check fails (e.g. intrinsic value >20x price, non-USD statements), `withheld`/`checks.failed` signal this, and a withheld call is not charged. It also discloses the cost model (first brief per UTC day free per key and per keyless address, 0.30 credits after) and the fx/currency_unverified flag semantics.

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 the trigger condition and the return payload, then the withholding/fx behavior, then input and pricing — a logical order with no filler sentences. Minor redundancy: the free-tier and credit pricing is stated twice (once in prose, once in the trailing parenthetical with the endpoint URL).

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?

There is no output schema, so the description carries the full burden of explaining return values, and it does: every figure's unit, period, as-of date and sec.gov source link, plus the `checks` list, `withheld`, `fx`, and `currency_unverified` fields. For a single-parameter read tool with rich response semantics, nothing an agent needs before calling is missing.

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?

Schema description coverage is 100%, so the ticker pattern and example are already documented in the schema. The description only restates the parameter as "`ticker` (path), e.g. GET /brief/KO," adding no format or edge-case meaning beyond what the schema provides; 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 and a precise composite resource: intrinsic value per share, owner-earnings value, margin of safety, verdict sentence, top 13F holders, and company profile. An agent can immediately see this is the superset one-shot call and tell it apart from siblings like intrinsic_value, verdict, or guru_holdings.

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?

"Call this first when asked whether a listed company looks cheap or expensive, what it is worth, or which well-known investors own it" gives explicit trigger conditions and priority ordering relative to other tools. It stops short of naming when-not to use it or pointing to specific sibling alternatives for narrower questions (e.g. only 13F history), so it is clear context rather than full routing guidance.

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