Skip to main content
Glama

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Create Research Report

create_report
Idempotent

Synchronously generate a research report and persist it under the caller's authorship. One subtype, reverse_dcf:

• reverse_dcf — solves the stage-1 free-cash-flow growth rate the market price implies, with a 5×5 sensitivity grid across WACC × terminal-growth assumptions. Returns full markdown + structured JSON + every numerical claim's citation chain to the originating SEC accession.

Thesis reports were retired in 3.14.0 (report_type: "thesis" is refused); stored ones still read, render and list.

Tier: sample tier rejected — reports are per-author state.

Input Schema

NameRequiredDescriptionDefault
titleNoOptional human-supplied title; auto-generated when omitted.
paramsNoReverse-DCF parameters — required for report_type=reverse_dcf.
tickerNoUS-listed ticker — required for report_type=reverse_dcf. Case-insensitive.
report_typeYesSubtype. Only `reverse_dcf` is created now (requires ticker + params); thesis reports were retired in 3.14.0 and stored ones still read.
idempotency_keyNoOptional key for at-most-once semantics. Same key from the same user always yields the same report id.

Output Schema

NameRequiredDescriptionDefault
_metaYesProvenance envelope — data lineage for every MCP response
reportYes
markdownYes
sectionsYes
citationsYes
structuredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / report_type / description
      Previous value: -"Subtype. `reverse_dcf` requires ticker + params; `thesis` requires thesis_id (from save_thesis / list_theses)."New value: +"Subtype. Only `reverse_dcf` is created now (requires ticker + params); thesis reports were retired in 3.14.0 and stored ones still read."
    • changedInput schema / properties / report_type / enum
      Previous value: -[
      -  "reverse_dcf",
      -  "thesis"
      -]New value: +[
      +  "reverse_dcf"
      +]
    • removedInput schema / properties / thesis_id
      Removed value: -{
      -  "description": "Id of a saved thesis owned by the caller — required for report_type=thesis.",
      -  "maxLength": 64,
      -  "minLength": 1,
      -  "type": "string"
      -}
  2. Changed1 schema field changed
    • changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description
      Previous value: -"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."New value: +"payg_charge = real pay-per-call charge (a card or MPP payment through agent-pay). payg_rate_card = indicative price, not billed."
  3. Changed2 schema fields changed
    • changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description
      Previous value: -"payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed."New value: +"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."
    • changedOutput schema / properties / _meta / properties / cost_usd / properties / billed / description
      Previous value: -"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free."New value: +"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value only: no charge was made for this call (it was within your plan)."
  4. Added
  5. Removed
  6. Changed1 schema field changed
    • changedOutput schema / properties / _meta / properties / fundamentals_as_of / description
      Previous value: -"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to."New value: +"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt in bulk. Use THIS — not `last_updated` — when telling a user how current the cross-sectional fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to. It is a floor for a single filer, not a ceiling: a filer with a live partition receives its filing, facts and ratios intraday (minutes after EDGAR dissemination), so an entity-scoped read may carry a filing newer than this; cross-sectional ranks (factor scores, earnings signals) refresh with the weekly bulk export."
  7. Changed2 schema fields changed
    • addedOutput schema / properties / _meta / properties / fundamentals_as_of
      Added value: +{
      +  "description": "ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / _meta / properties / price_as_of
      Added value: +{
      +  "description": "ISO timestamp when the price surfaces were last refreshed.",
      +  "type": "string"
      +}
  8. Changed2 schema fields changed
    • addedOutput schema / properties / _meta / properties / cost_usd
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Per-call cost transparency. Omitted for subscription-only tools that have no PAYG-equivalent price.",
      +  "properties": {
      +    "amount_usd": {
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    "basis": {
      +      "description": "payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed.",
      +      "enum": [
      +        "payg_charge",
      +        "payg_rate_card"
      +      ],
      +      "type": "string"
      +    },
      +    "billed": {
      +      "description": "true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "amount_usd",
      +    "billed",
      +    "basis"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / _meta / properties / latency_ms
      Added value: +{
      +  "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
  9. Changed1 schema field changed
    • addedOutput schema / properties / _meta / properties / pit_safe / description
      Added value: +"true iff a zero-look-ahead point-in-time cut was applied to every returned figure"
  10. Changed9 schema fields changed
    • addedInput schema / properties / params / description
      Added value: +"Reverse-DCF parameters — required for report_type=reverse_dcf."
    • removedInput schema / properties / report_type / const
      Removed value: -"reverse_dcf"
    • changedInput schema / properties / report_type / description
      Previous value: -"Report type. PR 3 supports `reverse_dcf` only; additional types ship later."New value: +"Subtype. `reverse_dcf` requires ticker + params; `thesis` requires thesis_id (from save_thesis / list_theses)."
    • addedInput schema / properties / report_type / enum
      Added value: +[
      +  "reverse_dcf",
      +  "thesis"
      +]
    • addedInput schema / properties / thesis_id
      Added value: +{
      +  "description": "Id of a saved thesis owned by the caller — required for report_type=thesis.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / ticker / description
      Previous value: -"US-listed ticker — case-insensitive, normalised to upper."New value: +"US-listed ticker — required for report_type=reverse_dcf. Case-insensitive."
    • changedInput schema / required
      Previous value: -[
      -  "report_type",
      -  "ticker",
      -  "params"
      -]New value: +[
      +  "report_type"
      +]
    • removedOutput schema / properties / report / properties / report_type / const
      Removed value: -"reverse_dcf"
    • addedOutput schema / properties / report / properties / report_type / enum
      Added value: +[
      +  "reverse_dcf",
      +  "thesis"
      +]
  11. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) it discloses that the call is synchronous/blocking, that output includes markdown plus structured JSON plus a per-claim citation chain to SEC accessions, and that reports are per-author state rather than sample-tier shared data. The retired-thesis refusal behavior is also real context an agent needs. Loses a point only because the tier sentence is terse to the point of obscurity.

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 verb sentence, then a scannable subtype bullet, then retirement notice. Every block earns its place except the final 'Tier: sample tier rejected — reports are per-author state' line, which is compressed into near-unreadability and reads like an internal note.

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?

For a five-param nested creation tool with an output schema, the description covers the one live subtype, required inputs, blocking behavior, persistence/ownership, and the deprecated path. An agent has everything needed to call it correctly and to avoid the thesis trap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: it ties `params` to a 5×5 WACC × terminal-growth sensitivity grid, which explains what those two numeric inputs drive rather than merely restating their defaults. It also confirms ticker + params are required for the only live subtype, which the schema expresses only through a prose field description.

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 first sentence gives a specific verb and resource plus the persistence semantics ('generate a research report and persist it under the caller's authorship'), and the subtype block states exactly what the one supported report type computes. This clearly separates it from compute_dcf (calculation only) and save_freeform_report / update_report (other creation paths), even though those siblings are not named.

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?

It usefully warns that `report_type: "thesis"` is refused in 3.14.0 while stored thesis reports still read, which prevents a failed call. But it never states when to call this versus compute_dcf, save_freeform_report, or compute_accretion_dilution — the closest non-persisting alternatives — leaving that routing to inference.

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.