Skip to main content
Glama
Calera-Labs

FINSEC — Certified SEC Memory MCP Server

by Calera-Labs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

Get Certified SEC Valuation Pack

valuation_inputs
Read-only

Retrieve certified SEC/EDGAR valuation inputs, including historical free cash flow and screening packs like DCF, Piotroski, and Beneish, for a given company and period.

Instructions

Certified SEC/EDGAR valuation inputs pack (12 packs including dcf_valuation_inputs historical FCF). Not market EV, P/E, trading DCF, or macro gauges (Buffett Indicator / CAPE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packYesCertified SEC valuation pack ID (equity_screen, ev_bridge, quality_of_earnings, segment_mix, returns_screen, leverage_screen, piotroski_f, altman_z_prime, beneish_m_score, dupont_5step, working_capital_efficiency, dcf_valuation_inputs)
periodNoOptional reporting period, e.g. FY2023, Q3 FY2023. Defaults to FY2023 if omitted.
companyYesCompany ticker or name, e.g. AAPL, TSLA, MSFT
low_tokensNoOptional. When true, returns compact JSON schema.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stNoCompact status indicator (OK | REFUSE)
perNoCompact period string
valNoCompact numeric value
hashNoCryptographic filing audit hash
cellsNoValuation pack verified cells dictionary
valueNoVerified financial metric numeric value or computed arithmetic result
periodNoFiscal reporting period
reasonNoExplanation when SAFE_REFUSAL is returned
statusNoVerification status: VERIFIED_SUCCESS | SAFE_REFUSAL | COMPLETE | OK
companyNoCompany name or ticker symbol
conceptNoUS-GAAP / XBRL financial concept
operandsNoUnderlying verified metric operands with accessions
formattedNoFormatted monetary or percentage string
provenanceNoSEC EDGAR filing provenance details

Schema Changelog

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

  1. Changed16 schema fields changedv0.1.1
    • addedOutput schema / properties / cells
      Added value: +{
+  "description": "Valuation pack verified cells dictionary",
+  "type": "object"
+}
    • addedOutput schema / properties / company
      Added value: +{
+  "description": "Company name or ticker symbol",
+  "type": "string"
+}
    • addedOutput schema / properties / concept
      Added value: +{
+  "description": "US-GAAP / XBRL financial concept",
+  "type": "string"
+}
    • removedOutput schema / properties / content
      Removed value: -{
-  "description": "List of MCP output blocks containing verified SEC fact payload or SAFE_REFUSAL",
-  "items": {
-    "properties": {
-      "text": {
-        "description": "Serialized verified SEC fact response with cryptographic filing provenance",
-        "type": "string"
-      },
-      "type": {
-        "description": "MIME content type (text)",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "text"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / formatted
      Added value: +{
+  "description": "Formatted monetary or percentage string",
+  "type": "string"
+}
    • addedOutput schema / properties / hash
      Added value: +{
+  "description": "Cryptographic filing audit hash"
+}
    • addedOutput schema / properties / operands
      Added value: +{
+  "description": "Underlying verified metric operands with accessions",
+  "type": "array"
+}
    • addedOutput schema / properties / per
      Added value: +{
+  "description": "Compact period string",
+  "type": "string"
+}
    • addedOutput schema / properties / period
      Added value: +{
+  "description": "Fiscal reporting period",
+  "type": "string"
+}
    • addedOutput schema / properties / provenance
      Added value: +{
+  "description": "SEC EDGAR filing provenance details",
+  "type": "object"
+}
    • addedOutput schema / properties / reason
      Added value: +{
+  "description": "Explanation when SAFE_REFUSAL is returned",
+  "type": "string"
+}
    • addedOutput schema / properties / st
      Added value: +{
+  "description": "Compact status indicator (OK | REFUSE)",
+  "type": "string"
+}
    • addedOutput schema / properties / status
      Added value: +{
+  "description": "Verification status: VERIFIED_SUCCESS | SAFE_REFUSAL | COMPLETE | OK",
+  "type": "string"
+}
    • addedOutput schema / properties / val
      Added value: +{
+  "description": "Compact numeric value"
+}
    • addedOutput schema / properties / value
      Added value: +{
+  "description": "Verified financial metric numeric value or computed arithmetic result"
+}
    • changedOutput schema / required
      Previous value: -[
-  "content"
-]New value: +[]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already indicates non-destructive behavior. The description adds no further behavioral details about return format or potential side effects rule out any contradiction. It does not mention pagination, timeouts, or how the result is structured beyond 'compact JSON schema' in the low_tokens parameter, which is stated in the schema.

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?

Two sentences: first explains what it returns with an example pack, second clarifies exclusions. No redundant wording. Front-loaded with the core purpose ('Certified SEC valuation pack') and keeps it tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool returns a pack and has an output schema, the description covers the essential purpose and boundaries. It could mention that it provides historical and fundamental data, but the schema already details fields, and the surprise of exclusions (market EV, Buffett Indicator) is communicated. A minor gap is lack of a typical use case, but not critical.

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 for parameters is 100% (each parameter has a description). The tool description adds no extra semantics beyond what the schema already provides. It mentions 'including dcf_valuation_inputs historical FCF' which reinforces the pack parameter but does not delve into syntax or defaults beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it returns a 'Certified SEC/EDGAR valuation inputs pack' and enumerates the 12 packs (e.g., dcf_valuation_inputs). It also explicitly delimits its scope by saying 'Not market EV, P/E, trading DCF, or macro gauges', which sharpens the tool's purpose. Lacks a direct statement of what the agent should use the returned data for, but the title and examples suffice.

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?

Provides negative guidance (what it is not) but does not name alternative siblings or give explicit scenarios for when to use this tool over others. The description implies it is for certified SEC-based valuation inputs, but does not reference sibling tools or provide decision rules.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Calera-Labs/finsec-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server