Skip to main content
Glama
Sign In
Finance MCP

Finance MCP

by Blahaj-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Company Profile

get_company_profile
Read-onlyIdempotent

Fetch a consolidated company profile — business summary, SEC filings, insider activity, and price — in one call to answer open-ended questions about a stock.

Instructions

Everything worth knowing about a company, in one call. Start here for an open-ended question — and narrow it for a specific one.

Answers "tell me about X" without the caller needing to know which of the other tools to reach for: what the business is, what it filed with the SEC, what insiders and the market are doing, and where the stock trades. Sections are fetched concurrently, and each is labelled with how much weight its numbers carry — a figure taken from a filing is not the same kind of fact as one scraped from a third-party feed.

Ask for what you need. The default fetches eight sections; a narrow question does not need them. detail="brief" is roughly a third the size, and sections="business" (or any single one) is about a sixth — so "what sector is this?" costs a sixth of what "tell me about this company" does. Widen on a second call if the answer is not there; that is cheaper than fetching insider transactions and EDGAR filings for a question about a business summary.

Input Schema

NameRequiredDescriptionDefault
detailNo"brief" (business, financials, price), "standard" (the default eight), or "full" (everything, including the heuristic verdict and macro calendar).standard
symbolYesTicker symbol (e.g. MU, AAPL).
sectionsNoOverride which sections to include, comma-separated. Available: business, financials, earnings, filings, insiders, proposed, short, price, options, news, consensus, technicals, risk, macro.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, yet the description still adds real behavior: sections are fetched concurrently, and each figure is labelled by how much weight it carries because filing-derived numbers differ from scraped third-party data. It also quantifies payload cost (brief ≈ one third, single section ≈ one sixth). Missing only error behavior for an invalid or untickered symbol.

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?

Front-loaded with the core claim, then a bolded directive ("Ask for what you need"), then the cost facts — good ordering. Some redundancy: the first sentence and the "without the caller needing to know which of the other tools" clause make the same point, and the closing line restates the narrow-first advice already given.

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?

With no output schema, the description carries the return-value burden and does: it names the eight default sections, the extra content behind detail="full" (heuristic verdict, macro calendar), and the provenance labels attached to numbers. Combined with the concurrency and cost notes, an agent can call this correctly and predict the shape of the response.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines detail and sections, and the baseline is 3. The description goes beyond it by attaching relative cost to each mode and by framing sections as a narrowing override rather than a required choice, which shapes how an agent should combine detail and sections.

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?

States a specific verb and resource ("Everything worth knowing about a company, in one call") and immediately differentiates it from siblings: it answers "tell me about X" without the caller needing to know which of the other tools to reach for. The enumerated content areas (business, SEC filings, insiders, market, price) make the scope concrete.

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?

Explicitly prescribes when to use it (open-ended questions, "start here") versus when to narrow (a specific question should use sections/detail), and gives an escalation strategy: "Widen on a second call if the answer is not there." It also states why the alternative exists — that fetching insider transactions and EDGAR filings for a sector question is wasteful.

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

Deploy Server

Other Tools