Skip to main content
Glama
Sign In
FinzData

FinzData

Official
by finzdata-admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

company_profile

Retrieve a US stock or ETF reference profile by symbol to check listing details, sector, IPO date, price history range, and delisting status.

Instructions

Reference profile for a US stock or ETF: name, exchange, sector, industry, country, state, IPO date, first and last date of price history, and whether it is delisted. Dated data elsewhere on the free tier is limited to the last 12 months.

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": {
      "symbol": "<symbol>"
    },
    "name": "company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: the delisted flag, first/last dates of price history, and the free-tier 12-month coverage limitation. However, it says nothing about permissions, error behavior, or whether the symbol must be a US-listed ticker, so it is only partially complete.

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?

Two sentences, both load-bearing: the field inventory is front-loaded and the free-tier caveat follows. No filler, though the second sentence could be tied more explicitly to why it matters for this tool.

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 no output schema and no annotations, the description usefully enumerates return fields and notes the data coverage window. For a single-parameter reference lookup, this is close to sufficient; only permission/format details are missing.

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 0%, so the description should compensate. It implies the symbol is a US stock or ETF ticker, which adds some meaning beyond the bare 'Symbol' property, but it never clarifies format, exchange suffix, or case sensitivity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific resource (reference profile for a US stock or ETF) and enumerates the exact fields returned, so an agent can tell it apart from data-heavy siblings like fundamentals, prices_daily, and financial_statements. It lacks an explicit verb and never names a sibling, so it is clear but not maximally differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The closing note about free-tier data being limited to 12 months implies context about coverage but does not route the agent to or away from any sibling.

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