Skip to main content
Glama

FinBridge

FinBridge DB Schema

get_db_schema
Read-only

Inspect the schema of the local finbridge database (SQLite with ingested KR/US company fundamentals, filings, and daily prices): tables, views, columns, per-table row counts (counted in the background and refreshed every 30 minutes; null with rows_note "counting…" right after a server start), and ready-to-run example queries for query_db.

Read this before writing a query_db statement. It returns no company data itself — get_db_schema describes the tables, query_db runs the SELECT.

Args: (none)

Returns: {tables: [{name, columns: [{name, type}], rows}], views: [{name, columns: [{name, type}]}], examples: [sql_string]}

Key objects:

  • companies: KR companies have source='dart' + stock_code (6-digit), US companies source='edgar' + ticker

  • financials: one row per company x fiscal_year x quarter (quarter=0 = annual); raw unscaled KRW/USD amounts

  • prices_daily: daily OHLCV per company_id

  • views v_financials (financials joined with company name/ticker/stock_code) and v_latest_annual (latest annual row per company) — prefer these in query_db

  • filing_briefs: filing summaries keyed by (source, ext_key). Summary text is returned only for published summaries: a row withheld by the review checks (status='review') keeps its keys and dates with headline/facts/company_en/event_type/guards/engine NULL — the summaries get_disclosure_feed reports as summary_status='withheld_review'.

Examples:

  • Call before writing SQL for query_db, to learn table/column names.

  • Check row counts to see how much data the nightly ingest has loaded.

Use when: preparing a query_db, or checking ingest coverage. Don't use for market data itself (get_stock_prices / get_valuation read the same tables with the right joins already done). FinBridge has no real-time equity quote tool — equity prices here are end-of-day closes from the nightly ingest; the only live data is regulator filings (get_dart_filings / get_edgar_filings). Errors: 'database has not been built yet' — the ingest pipeline has not run on the server.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_db_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
viewsYes
tablesYes
examplesNo
rows_noteNo
data_as_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedOutput schema / properties / data_as_of / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / tables / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / tables / items / properties / columns / items / additionalProperties
      Previous value: -trueNew value: +{}
    • removedOutput schema / properties / tables / items / properties / columns / items / properties / type / $ref
      Removed value: -"#/properties/tables/items/properties/columns/items/properties/name"
    • addedOutput schema / properties / tables / items / properties / columns / items / properties / type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / views / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / views / items / properties / columns / items / additionalProperties
      Previous value: -trueNew value: +{}
    • removedOutput schema / properties / views / items / properties / columns / items / properties / name / $ref
      Removed value: -"#/properties/tables/items/properties/columns/items/properties/name"
    • addedOutput schema / properties / views / items / properties / columns / items / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / views / items / properties / columns / items / properties / type / $ref
      Removed value: -"#/properties/tables/items/properties/columns/items/properties/name"
    • addedOutput schema / properties / views / items / properties / columns / items / properties / type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / data_as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / rows_note
      Added value: +{
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only and non-destructive annotations, it discloses the background row-count refresh cadence, startup null behavior, nightly end-of-day pricing versus live filings, and the 'database has not been built yet' failure. It also explains raw unscaled financial amounts and withheld-review filing summaries, providing unusually useful operational context.

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 and uses labeled sections and bullets effectively, with most details supporting correct selection or SQL preparation. It is somewhat overlong for a zero-argument inspection tool, and the Args and Returns blocks repeat information already available in structured fields.

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?

It covers scope, important tables and views, key conventions, example-query availability, freshness, row-count timing, alternatives, and ingest-related failure. Together with the output schema and safety annotations, this leaves no material gap for selecting or invoking the tool correctly.

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?

There are no parameters, so the schema leaves no argument semantics requiring clarification and the baseline is 4. The explicit 'Args: (none)' confirms this but adds nothing beyond the structured 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 opening sentence names the operation, resource, database contents, and concrete outputs: tables, views, columns, row counts, and example queries. It also clearly distinguishes this metadata tool from query_db, which executes SELECT statements.

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?

It explicitly says to call the tool before writing query_db SQL and when checking ingest coverage. It also states when not to use it, routing market-data needs to get_stock_prices or get_valuation and identifying get_dart_filings and get_edgar_filings as the live-data tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.