FINSEC — Certified SEC Memory MCP Server

Query SEC Sector Peers

query_sec_sector_peers

Read-only

Retrieve certified SEC EDGAR financial metrics for a peer group derived from SIC codes and 10-K segment disclosures, enabling sector screening when no specific company ticker is provided.

Instructions

Returns certified SEC EDGAR XBRL metrics across an industry peer group dynamically derived from SEC filing SIC codes and 10-K business segment disclosures. Use this for sector screening or when no specific company ticker is provided.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Optional peer limit, default 5
`period`	No	Optional filing period, e.g. FY2025
`metrics`	No	Optional comma-separated or array of SEC XBRL metrics, e.g. Revenues,OperatingIncome,TotalLongTermDebt
`low_tokens`	No	Optional. When true, returns compact JSON schema.
`sector_or_industry`	Yes	Industry or sector description as declared in SEC filings, e.g. 'photonics', 'optics', 'semiconductors', 'pharmaceuticals', 'aerospace'

Output Schema

TableJSON Schema

Name	Required	Description
`st`	No	Compact status indicator (OK \| REFUSE)
`per`	No	Compact period string
`val`	No	Compact numeric value
`hash`	No	Cryptographic filing audit hash
`cells`	No	Valuation pack verified cells dictionary
`value`	No	Verified financial metric numeric value or computed arithmetic result
`period`	No	Fiscal reporting period
`reason`	No	Explanation when SAFE_REFUSAL is returned
`status`	No	Verification status: VERIFIED_SUCCESS \| SAFE_REFUSAL \| COMPLETE \| OK
`company`	No	Company name or ticker symbol
`concept`	No	US-GAAP / XBRL financial concept
`operands`	No	Underlying verified metric operands with accessions
`formatted`	No	Formatted monetary or percentage string
`provenance`	No	SEC EDGAR filing provenance details

Schema Changelog

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

Changed16 schema fields changedv0.1.1Aug 20, 2026

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: +[]

First observedv0.1.0Aug 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The readOnlyHint annotation already classifies this as safe, and the description adds context by describing dynamic peer-group construction from SEC filings and 10-K disclosures. It does not cover pagination or empty-result behavior, but the read-only disclosure plus source detail is adequate.

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 deliver the full core description: first establishes what the tool returns and how peers are derived, second states when to use it. No filler or repetition of elements that are already visible in structured metadata.

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?

With one required parameter, a high-coverage schema, readOnly annotation, and output schema present, the description is sufficiently complete for a peer-group query tool. It could include more explicit exclusion guidance, but the combination of description and structured metadata is not missing major context.

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 description coverage is 100%, so the input schema already documents all five parameters. The description adds general peer-group context but does not materially augment the detailed parameter descriptions in the 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 clearly states the tool returns certified SEC EDGAR XBRL metrics for an industry peer group, and explains that the peer group is dynamically derived from SIC codes and 10-K disclosures. It further differentiates from siblings by positioning it for sector screening and non-ticker-specific queries.

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 explicitly says to use this tool for sector screening or when no specific company ticker is provided, giving clear situational guidance. It does not name alternative ticker-level tools, so it falls just short of a full when-not/alternatives explanation.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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