Skip to main content
Glama

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein
OverviewDiscussionsAdmin

Forensic accounting check

forensic_audit
Read-onlyIdempotent

Returns forensic accounting scores from a company's two latest annual filings: a partial Beneish M-score (sales growth, total accruals and leverage growth), Sloan accruals, debt to equity, debt to assets and return on assets, and plain-language red flags, with the source filing. Use this when the user asks about earnings quality or accounting risk. The M-score is partial because some of its inputs are not in the dataset, and the result marks it so.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesTicker symbol or SEC CIK of the company to check, e.g. AAPL.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_metaYesProvenance envelope — data lineage for every MCP response
resultYes
tickerYes
sec_urlYes
period_endYes
source_filingYes
prior_period_endYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol of the company to audit, e.g. AAPL, MSFT, BRK.B."New value: +"Ticker symbol or SEC CIK of the company to check, e.g. AAPL."
    • removedOutput schema / properties / _meta / properties / cost_usd
      Removed 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"
-}
    • removedOutput schema / properties / _meta / properties / data_plan
      Removed value: -{
-  "description": "Access plan: sample | sp500 | pro | full",
-  "type": "string"
-}
    • changedOutput schema / properties / _meta / properties / fundamentals_as_of / description
      Previous 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."New value: +"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."
    • removedOutput schema / properties / _meta / properties / last_updated
      Removed value: -{
-  "description": "ISO timestamp when the snapshot was exported",
-  "type": "string"
-}
    • removedOutput schema / properties / _meta / properties / latency_ms
      Removed value: -{
-  "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
-  "minimum": 0,
-  "type": "integer"
-}
    • removedOutput schema / properties / _meta / properties / limit_warnings
      Removed value: -{
-  "description": "Soft-warning array for partial fulfillment. Each entry carries a stable subcode + remediation.options[]. AI agents pattern-match on subcode.",
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "const": "LIMIT_EXCEEDED",
-        "type": "string"
-      },
-      "current_plan": {
-        "type": "string"
-      },
-      "extensions": {
-        "additionalProperties": {},
-        "type": "object"
-      },
-      "limit_type": {
-        "type": "string"
-      },
-      "limit_value": {},
-      "remediation": {
-        "additionalProperties": true,
-        "properties": {
-          "contact_sales": {
-            "type": "string"
-          },
-          "default_action": {
-            "type": "string"
-          },
-          "options": {
-            "items": {
-              "additionalProperties": {},
-              "type": "object"
-            },
-            "type": "array"
-          },
-          "pricing_page": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "options",
-          "default_action",
-          "pricing_page",
-          "contact_sales"
-        ],
-        "type": "object"
-      },
-      "requested_value": {},
-      "returned_value": {},
-      "subcode": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "code",
-      "subcode",
-      "limit_type",
-      "current_plan",
-      "remediation"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedOutput schema / properties / _meta / properties / payg_override
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Set when this single response was paid for via the agent-pay PAYG flow — the rate-limit / depth-limit checks were bypassed for this call only.",
-  "properties": {
-    "amount_cents": {
-      "type": "number"
-    },
-    "entity_scope_hash": {
-      "type": "string"
-    },
-    "meter": {
-      "type": "string"
-    },
-    "quote_id": {
-      "type": "string"
-    },
-    "retry_token_hash": {
-      "type": "string"
-    },
-    "ticker_count": {
-      "type": "number"
-    },
-    "tool": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "quote_id",
-    "tool",
-    "meter",
-    "amount_cents",
-    "ticker_count",
-    "entity_scope_hash",
-    "retry_token_hash"
-  ],
-  "type": "object"
-}
    • removedOutput schema / properties / _meta / properties / rate_limit
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Caller's remaining budget",
-  "properties": {
-    "limit": {
-      "type": "integer"
-    },
-    "remaining": {
-      "type": "integer"
-    },
-    "reset_at": {
-      "description": "ISO 8601 timestamp when the window resets",
-      "type": "string"
-    },
-    "window": {
-      "enum": [
-        "minute",
-        "hour"
-      ],
-      "type": "string"
-    }
-  },
-  "required": [
-    "limit",
-    "remaining",
-    "reset_at",
-    "window"
-  ],
-  "type": "object"
-}
    • removedOutput schema / properties / _meta / properties / request_id
      Removed value: -{
-  "description": "Per-request correlation id (8-char)",
-  "type": "string"
-}
    • removedOutput schema / properties / _meta / properties / schema_version
      Removed value: -{
-  "description": "Parquet schema version from manifest.json",
-  "type": "string"
-}
    • removedOutput schema / properties / _meta / properties / snapshot
      Removed value: -{
-  "description": "Snapshot directory name (e.g. snapshot_20260420)",
-  "type": "string"
-}
    • removedOutput schema / properties / _meta / properties / truncation / properties / current_plan
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / _meta / properties / truncation / properties / upgrade_required_for
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / _meta / properties / truncation / properties / upgrade_url
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / _meta / required
      Previous value: -[
-  "data_plan",
-  "schema_version",
-  "snapshot",
-  "last_updated",
-  "source",
-  "pit_safe"
-]New value: +[
+  "source",
+  "pit_safe"
+]
  2. 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."
  3. 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"
+}
  4. 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"
+}
  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 / ticker / description
      Added value: +"Stock ticker symbol of the company to audit, e.g. AAPL, MSFT, BRK.B."
  7. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safe, read-only, idempotent profile. The description adds meaningful non-obvious context: the M-score is partial because some inputs are absent and the result marks this limitation, preventing misinterpretation of the output.

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?

The description is front-loaded with the return value and then the usage condition. It is slightly long because it enumerates every metric, but every clause carries specific information relevant to invoking the tool.

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, annotations, and fully documented single parameter, the description provides all the context an agent needs: what is computed, what caveat to expect, and when to call it. Nothing essential 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?

The schema fully documents the single ticker parameter, including CIK support and an example. The description adds no parameter-specific detail, so the baseline of 3 for high schema coverage is appropriate.

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 gives a specific verb ('Returns'), resource ('forensic accounting scores'), and enumerates exactly what is computed: partial Beneish M-score components, Sloan accruals, leverage ratios, and red flags. This clearly separates it from generic siblings like get_financial_ratios or get_earnings_signals.

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?

It provides a clear usage trigger: 'Use this when the user asks about earnings quality or accounting risk.' However, it does not name alternative tools or state when not to use it, leaving routing to the agent's inference.

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