Skip to main content
Glama

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein

Update Report Sections

update_report
Idempotent

Replace one or more sections of an existing report owned by the caller. Useful for authoring workflows where the agent's first draft (create_report) is refined by additional analysis before publishing. Pass citations for figures in the edited prose — they are MERGED into the report's existing set, never replacing it, so omitting them preserves the lineage already recorded. Bumps version. Does NOT change price / tier / visibility — use publish_report for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional new title.
abstractNoOptional new abstract.
sectionsYesSections to replace. Sections not listed are preserved — to DELETE one, name it in `remove_section_ids`. Section ids must match the existing payload.
citationsNoLineage for figures in the edited sections. MERGED into the report's existing citations (first claim wins), never replacing them — so an editor autosave that sends none preserves every citation the report already had.
report_idYesIdentifier of the report to update, as returned by create_report or list_my_reports.
expected_versionNoOptimistic concurrency check. If supplied and the current HEAD version is different, the call returns a `version_conflict` error WITHOUT writing. Pass the version you loaded so a concurrent agent edit produces a 'conflict — review' UX instead of silently overwriting (eng review A3A).
remove_section_idsNoSection ids to DELETE outright. Without this, a merge-only update cannot express a deletion: an editor that drops a section simply omits it, the omitted section is preserved, and the caller sees a bumped version with the deleted content still there — a save that reports success and changed nothing. Ids must exist, and the last remaining section cannot be removed (a report with no sections is unreadable); remove the report instead with delete_report.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_metaYesProvenance envelope — data lineage for every MCP response
reportYes
versionYes
archivedYes
previous_versionYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / citations
      Added value: +{
+  "description": "Lineage for figures in the edited sections. MERGED into the report's existing citations (first claim wins), never replacing them — so an editor autosave that sends none preserves every citation the report already had.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "accession_ids": {
+        "description": "Optional SEC accession ids backing the claim.",
+        "items": {
+          "maxLength": 32,
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 50,
+        "type": "array"
+      },
+      "claim": {
+        "description": "Plain-English claim, quoting the figure as the prose writes it (e.g. 'FY2024 revenue: $391.0B').",
+        "maxLength": 500,
+        "minLength": 1,
+        "type": "string"
+      },
+      "evidence": {
+        "description": "Provenance class. Defaults to 'derived' — the weaker claim.",
+        "enum": [
+          "primary",
+          "derived",
+          "external"
+        ],
+        "type": "string"
+      },
+      "fact_ids": {
+        "description": "Valuein fact_ids backing the claim, as returned by the data tools.",
+        "items": {
+          "maxLength": 128,
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 50,
+        "type": "array"
+      },
+      "filed_at": {
+        "description": "SEC acceptance timestamp of the filing (ISO 8601) — when the figure became public.",
+        "maxLength": 40,
+        "minLength": 1,
+        "type": "string"
+      },
+      "form_type": {
+        "description": "SEC form the figure was reported on ('10-K', '10-Q', '20-F'), verbatim from the source.",
+        "maxLength": 20,
+        "minLength": 1,
+        "type": "string"
+      },
+      "period_end": {
+        "description": "Last day of the period the figure COVERS (YYYY-MM-DD). Not the filing date.",
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "period_label": {
+        "description": "How the filer names that period: 'FY2025', 'Q3 2025'.",
+        "maxLength": 40,
+        "minLength": 1,
+        "type": "string"
+      },
+      "sec_urls": {
+        "description": "Optional EDGAR URLs, one per accession.",
+        "items": {
+          "maxLength": 500,
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 50,
+        "type": "array"
+      },
+      "ticker": {
+        "description": "Ticker the fact belongs to. Lets a figure be verified when the report has no ticker.",
+        "maxLength": 10,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "claim",
+      "fact_ids"
+    ],
+    "type": "object"
+  },
+  "maxItems": 1000,
+  "type": "array"
+}
    • addedInput schema / properties / remove_section_ids
      Added value: +{
+  "description": "Section ids to DELETE outright. Without this, a merge-only update cannot express a deletion: an editor that drops a section simply omits it, the omitted section is preserved, and the caller sees a bumped version with the deleted content still there — a save that reports success and changed nothing. Ids must exist, and the last remaining section cannot be removed (a report with no sections is unreadable); remove the report instead with delete_report.",
+  "items": {
+    "maxLength": 128,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}
    • changedInput schema / properties / sections / description
      Previous value: -"Sections to replace. Sections not listed are preserved. Section ids must match the existing payload."New value: +"Sections to replace. Sections not listed are preserved — to DELETE one, name it in `remove_section_ids`. Section ids must match the existing payload."
    • removedInput schema / properties / sections / items / properties / heading / minLength
      Removed value: -1
    • removedInput schema / properties / sections / items / properties / markdown / minLength
      Removed value: -1
  2. 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"
+}
  3. 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"
+}
  4. Changed2 schema fields changed
    • removedOutput schema / properties / vectorize_reindexed
      Removed value: -{
-  "type": "boolean"
-}
    • changedOutput schema / required
      Previous value: -[
-  "_meta",
-  "report",
-  "vectorize_reindexed",
-  "version",
-  "previous_version",
-  "archived"
-]New value: +[
+  "_meta",
+  "report",
+  "version",
+  "previous_version",
+  "archived"
+]
  5. 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"
  6. Changed1 schema field changed
    • addedInput schema / properties / report_id / description
      Added value: +"Identifier of the report to update, as returned by create_report or list_my_reports."
  7. Changed4 schema fields changed
    • addedInput schema / properties / expected_version
      Added value: +{
+  "description": "Optimistic concurrency check. If supplied and the current HEAD version is different, the call returns a `version_conflict` error WITHOUT writing. Pass the version you loaded so a concurrent agent edit produces a 'conflict — review' UX instead of silently overwriting (eng review A3A).",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / properties / archived
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / previous_version
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / required
      Previous value: -[
-  "_meta",
-  "report",
-  "vectorize_reindexed",
-  "version"
-]New value: +[
+  "_meta",
+  "report",
+  "vectorize_reindexed",
+  "version",
+  "previous_version",
+  "archived"
+]
  8. Added

TDQS

A4.1/5.0
Behavior1/5

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

The description says 'Bumps version' and describes an optimistic concurrency check via expected_version, implying that repeated identical calls change state (version number) and can fail with conflicts. This directly contradicts the annotation idempotentHint=true, which suggests the operation is safe to retry without side effects. This is a clear annotation contradiction, so the score is 1 per rubric.

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?

The description is long but every sentence earns its place. It front-loads the primary purpose, then adds essential behavioral detail (merge semantics, version bump, non-changes) without redundancy. The structure helps the agent quickly grasp what the tool does and what to be careful about.

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?

Given the output schema and annotations, the description covers all important operational aspects: it specifies ownership, workflow context, what is not changed, deletion semantics, merge behavior, and concurrency. It also references sibling tools (create_report, publish_report) for guidance. This makes the description complete for a complex update tool.

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?

The schema covers 100% of parameters, so the baseline is 3. However, the description adds significant semantic detail beyond the schema: citations are MERGED (first claim wins), remove_section_ids is required to express deletion, and expected_version produces a version_conflict error without writing. A minor gap is that it doesn't explicitly mention title/abstract can be updated in the same call even though sections is required, but the schema already documents those fields.

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 description opens with a specific verb and resource: 'Replace one or more sections of an existing report owned by the caller.' This clearly distinguishes the tool from siblings like create_report, publish_report, and delete_report, and it specifies the scope of what can be replaced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool ('authoring workflows where the agent's first draft (create_report) is refined by additional analysis before publishing'), and it names an alternative for excluded actions ('use publish_report' for price/tier/visibility changes). It also clarifies when not to use it implicitly by listing what it does NOT change.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Valuein — SEC EDGAR Fundamentals & Smart-Money Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool has a distinct purpose with detailed descriptions that clarify differences. Overlaps like get_peer_comparables vs screen_universe are well-differentiated by scope (single company vs cross-sectional). Similarly, get_insider_sentiment vs get_smart_money_flow are clearly distinguished by data sources and methodology.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., create_report, get_financial_ratios, delete_alert). No mixing of conventions or inconsistent verbs.

Tool Count2/5

With 69 tools, the count far exceeds the 25+ threshold for 'too many'. While the domain is broad, the sheer volume likely overwhelms agents and increases selection complexity.

Completeness4/5

The tool set covers a wide range of SEC filings, ratios, smart-money data, alerts, reports, and more. Minor gaps exist (e.g., no options or detailed debt data), but most analyst workflows are supported.

Resources