Skip to main content
Glama
Calera-Labs

FINSEC — Certified SEC Memory MCP Server

by Calera-Labs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

VLN Capabilities Overview

vln_capabilities_overview
Read-only

Discover all certified EDGAR valuation packs, financial arithmetic operations, SEC calculations, and scope boundaries in one structured overview. Quickly identify available capabilities for your SEC data tasks.

Instructions

Returns a complete structured overview of all certified EDGAR valuation packs, deterministic financial arithmetic operations, SEC calculations, and product scope boundaries on finsec.caleralabs.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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

A4.5/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description does not contradict that. It adds context about the content returned (pack types, operations, scope), which goes beyond the annotation. The description provides a clear picture of what the tool reveals without side effects.

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 a single, information-dense sentence that lists the exact contents of the overview. No wasted words, well-structured and front-loaded with the core action.

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 presence of an output schema and read-only annotation, the description sufficiently covers what the tool does. It is appropriately detailed for a capabilities overview tool and complements the structured metadata.

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 input schema already documents the sole parameter (low_tokens) with full coverage. The description does not mention the parameter or add any extra meaning beyond what the schema provides. Baseline 3 is appropriate since schema coverage is 100%.

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 clearly states the tool returns a structured overview of multiple specific domains (EDGAR valuation packs, financial arithmetic, SEC calculations, scope). It distinguishes itself from sibling tools that perform specific calculations (e.g., compute_sec_cagr) by being the overview/summary tool.

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?

The description implies usage when one needs a broad overview of capabilities. It does not explicitly mention alternatives or when not to use it, but context with siblings makes it clear. Slightly below perfect due to lacking explicit exclusions.

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