Skip to main content
Glama

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein
OverviewDiscussionsAdmin

Publish Report (free)

publish_report
Idempotent

Publish a report for FREE at listed or unlisted visibility to build your public author profile. listed makes it discoverable via search_reports (keyword catalog search); unlisted keeps it out of the catalog but accessible by direct id (shareable link). Author can set a tier_required no higher than their own plan. All listings are free today (omit price_cents or set it to 0); paid listings are a future capability. ⚠️ VERIFIED BEFORE IT GOES OUT: every figure is checked against the filing it cites, and the publish is REFUSED (FIGURES_UNVERIFIED) if any number the filing contradicts has not been reviewed by a human. Call verify_report_figures FIRST and fix each differs — quote the filing's own display string with update_report, or record a disposition with save_figure_review. Figures that merely could not be checked do NOT block publishing. If verification itself is unreachable the publish is refused as VERIFICATION_UNAVAILABLE (retryable) rather than going out unchecked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_idYes
visibilityNolisted
price_centsNoCurrently must be omitted or 0 — all listings are free. A non-zero value is rejected until paid listings ship.
tier_requiredNoMinimum subscriber tier to read the full body. Defaults to the author's plan.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  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_indexed
      Removed value: -{
-  "type": "boolean"
-}
    • changedOutput schema / required
      Previous value: -[
-  "_meta",
-  "report",
-  "vectorize_indexed"
-]New value: +[
+  "_meta",
+  "report"
+]
  5. Added
  6. Removed
  7. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations provide only idempotentHint=true and non-destructive/read-only flags. The description adds substantial behavioral detail: publishing is refused with FIGURES_UNVERIFIED if contradicted figues are not reviewed, VERIFICATION_UNAVAILABLE is retryable, unlisted items stay out of the catalog, and paid listings are a future capability. It also clarifies that uncheckable figues do not block publishing. This fully informs the agent of the tool's real-world behavior.

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 densely packed with necessary operational detail. It front-loads the core purpose, then gives visibility semantics, tier and price constraints, and the verification workflow in a logical order. Every sentence contributes actionable information; the forced-verification warning is prominent and justified by its importance.

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 tool's complexity, the description covers prerequisites, verification failure modes, resolution steps, retry behavior, and pricing constraints. An output schema exists, so return-value documentation is unneccesary. The agent has everything needed to invoke this tool correctly and know what will happen.

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

Parameters5/5

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

Although schema description coverage is only 50%, the description richly explains the key parameters: what listed vs unlisted means for discoverability, that tier_required cannot exceed the author's plan, and that price_cents must be omitted or 0. This adds meaning well beyond the enum and default values in the input schema.

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 states a specific verb and resource: 'Publish a report for FREE at listed or unlisted visibility.' It immediately distinguishes itself from siblings like publish_claim and publish_thesis by focusing on reports and by explaining the visibility options. The explicit public-profile goal further clarifies the tool's unique role.

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 gives concrete when-to-use guidance, including calling verify_report_figures FIRST, fixing every 'differs' with update_report or save_figure_review, and the retryable behavior when verification is unreachable. It also sets clear expectations about pricing, making it obvious when to omit price_cents. This goes beyond general context into actionable sequencing and fallback conditions.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources