Skip to main content
Glama

AI multi-analyst research briefing (HEADLINE)

research
Read-only

Full briefing, bull case, bear case, valuation, investment plan and intrinsic-value range as one structured JSON document. 0.25 credits ($0.25) per successful call, ai_research quota 50/day. Returns the latest completed briefing for the ticker — the same one its public company page shows; a fresh run cannot be started through the API yet (404 when none exists). Not in the sandbox. Keyless trial: with no key and no payment, each IP gets one call every 7 days at no charge (header X-DV-Keyless-Trial says when the next one opens; a 404 or 5xx does not use it). After that, send a live key, or pay this one call with x402 (no key needed); the 402 says the trial was used and when it resets (keyless_trial.resets_at). Same price as /brief, a different product: /brief is a short valuation answer computed at call time; this is the full written briefing. (GET https://app.deepvalues.ai/api/v1/research/{ticker}, e.g. https://app.deepvalues.ai/api/v1/research/AAPL — 0.25 credits per call; one call with no credentials per address every 7 days, at no charge (the keyless research trial); after that it needs a connected account or a dv_sk_ key) Missing data? Call request_data.

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": "research"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesThe real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}.
languageNoEnglish

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ticker / description
      Added value: +"The real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses cost (0.25 credits per successful call), the ai_research quota (50/day), that it returns a cached latest briefing rather than triggering a run, the 404-when-none-exists case, sandbox exclusion, and the full keyless-trial and x402 fallback mechanics including the X-DV-Keyless-Trial header and keyless_trial.resets_at. It also clarifies that failed 404/5xx calls do not consume the trial. This is unusually rich behavioral disclosure for a read-only tool and is consistent with readOnlyHint=true.

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 what-it-returns and pricing lead, which is good front-loading. However, the pricing, keyless-trial, and URL information is stated twice – once in prose and again in a long parenthetical that re-lists '0.25 credits per call' and 'one call with no credentials per address every 7 days' – so a substantial fraction of the text does not earn its place. The trailing 'Missing data? Call request_data' is useful but tacked on without structure.

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 must describe the return value, and it does so explicitly (component list plus 'structured JSON document'). Combined with cost, quota, auth paths, error semantics, and the cached-vs-fresh caveat, an agent has everything needed to call it correctly and interpret failures.

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 coverage is 50% – `ticker` is documented in the schema (including share-class forms) and `language` is a self-describing enum with a default. The description reinforces ticker usage via the URL example and path substitution note but adds nothing about `language` semantics (e.g. whether it affects the whole briefing). Baseline 3 is appropriate since the schema carries most of the load.

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?

The opening sentence names the exact deliverable and its components (bull case, bear case, valuation, investment plan, intrinsic-value range) as one structured JSON document. It then explicitly distinguishes itself from the sibling `brief`: '/brief is a short valuation answer computed at call time; this is the full written briefing.' An agent can choose between the two without opening either page.

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?

Clear conditions are given: use it to retrieve the latest completed briefing, note that a fresh run cannot be started via API, and it routes to `request_data` for missing data. The /brief alternative is named with the exact condition that separates them. It stops short of a full when-not-to-use statement (e.g. what to do instead when no briefing exists), which keeps it at 4.

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