Skip to main content
Glama

FinBridge

Daily Stock Prices (FinBridge DB)

get_stock_prices
Read-only

Get daily OHLCV price history from the local finbridge database (populated by the nightly ingest jobs). Rows are returned newest first.

Listed equities and ETFs. Japan and Europe carry no prices at all, and crypto is not served.

Price coverage by market — we only store what we have redistribution rights to:

  • Korea (DART + Financial Services Commission): full daily history, corporate-action adjusted. SERVED (latest values for attested personal paid subscribers, otherwise delayed by at least 20 minutes; completed trading days only, up to 30 rows per call; personal use only).

  • Taiwan (TWSE OpenAPI, Open Government Data License): daily history. SERVED.

  • US (consolidated end-of-day equities feed): daily history from 2023-03-28. PAUSED for customer accounts (see the server NOTICE). Split-adjusted; dividend-adjusted closes exist where SEC-reported dividends do (adj_close).

  • Japan: NOT served. EDINET publishes disclosure documents, not prices, so we hold Japanese filings and the company master but no quotes.

Args:

  • company: a ticker (US 'AAPL', TW/JP 4-digit '2330'), a KR 6-digit stock code ('005930'), or a company name in the local language or English ('TSMC', 'Toyota', '삼성전자'). Resolution priority: exact ticker > 6-digit KR code > exact name (name or English name) > partial name (multiple partial matches return a candidate list error).

  • from / to: optional YYYY-MM-DD range bounds (inclusive)

  • limit: max rows, 1-500 (default 60)

  • response_format: 'markdown' (default) or 'json'

Account limits: a free account includes the most recent 130 trading sessions of each name. Results follow the current account's history entitlement. When the window is trimmed the response carries a plan_limit field saying so.

Returns: {company: {name, source, ticker|stock_code}, count, truncated, prices: [{date, open, high, low, close, volume}]} — newest date first; truncated=true means older rows exist beyond 'limit'.

Examples:

  • {company: '005930', limit: 30} -> last 30 KR trading days for Samsung Electronics

  • {company: '005930', from: '2026-01-01', to: '2026-06-30'} -> Samsung Electronics H1 2026

Use when: historical closes/volumes for charting or return calculations from ingested data. Don't use for crypto, which is not served. 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: unknown company -> no-match or candidate-list error; JP/EU company -> no-prices error (those markets carry statements only); no price rows -> a market-specific hint (new listing, delisted, nightly lag).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "get_stock_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD (inclusive)
fromNoStart date YYYY-MM-DD (inclusive)
limitNoMax rows, 1-500 (default 60), newest first
companyYesKR 6-digit stock code (e.g. '005930') or company name
response_formatNo'markdown' for a table, 'json' for compact machine-readable outputmarkdown

Output Schema

NameRequiredDescriptionDefault
countYes
pricesYes
companyYes
truncatedNo
data_as_ofNo
data_notesNo
plan_limitNo
latest_quoteNo
koscom_noticeNo
realtime_accessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / realtime_access
      Added value: +{
      +  "additionalProperties": {},
      +  "properties": {},
      +  "type": "object"
      +}
  2. Changed28 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / company / additionalProperties
      Previous value: -trueNew value: +{}
    • removedOutput schema / properties / company / properties / cik / anyOf
      Removed value: -[
      -  {
      -    "type": [
      -      "string",
      -      "number"
      -    ]
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / company / properties / cik / type
      Added value: +[
      +  "string",
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / market / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / market / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / page_url / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / page_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / source / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / source / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / stock_code / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / stock_code / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / ticker / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / ticker / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • 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 / data_notes / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / koscom_notice / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / latest_quote / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / plan_limit / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / prices / items / additionalProperties
      Previous value: -trueNew value: +{}
    • removedOutput schema / properties / prices / items / properties / close / $ref
      Removed value: -"#/properties/prices/items/properties/open"
    • addedOutput schema / properties / prices / items / properties / close / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / prices / items / properties / high / $ref
      Removed value: -"#/properties/prices/items/properties/open"
    • addedOutput schema / properties / prices / items / properties / high / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / prices / items / properties / low / $ref
      Removed value: -"#/properties/prices/items/properties/open"
    • addedOutput schema / properties / prices / items / properties / low / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / prices / items / properties / volume / $ref
      Removed value: -"#/properties/prices/items/properties/open"
    • addedOutput schema / properties / prices / items / properties / volume / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / koscom_notice
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / latest_quote
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / data_notes
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
  5. Changed2 schema fields changed
    • addedOutput schema / properties / data_as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / plan_limit
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description goes far beyond them: per-market coverage and licensing, Korea's 20-minute delay and 30-row cap, US feed paused for customer accounts, the 130-session free-account entitlement, and the plan_limit/truncated response flags. This is exactly the operational context an agent needs before calling.

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 purpose and return ordering, then organized into market coverage, args, limits, returns, and examples. Slightly redundant — Japan/Europe exclusion is stated twice (opening line and the Japan section) — but the repetition is minor and the structure is easy to scan.

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?

For a five-parameter read tool with an output schema, the description covers everything an agent needs: coverage caveats, entitlement trimming, error taxonomy (no-match, candidate list, no-prices, market-specific hints), and return shape. Nothing material is left to inference.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning: accepted identifier formats per market (US 'AAPL', TW/JP 4-digit, KR 6-digit), the resolution priority order, and the candidate-list error on ambiguous partial names. It also documents limit bounds and the inclusive from/to semantics with worked examples.

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 ('Get daily OHLCV price history from the local finbridge database') and immediately scopes it to listed equities and ETFs, explicitly excluding Japan, Europe, and crypto. An agent can distinguish this from the filings-oriented siblings without opening any schema.

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?

Has an explicit 'Use when' clause (historical closes/volumes for charting or return calculations) and a 'Don't use' clause (crypto not served). It also names the correct alternatives for live data (get_dart_filings / get_edgar_filings) and clarifies there is no real-time equity quote tool, which prevents a common mis-selection.

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.