Get a company's profile — sector, market cap, price, P/E ratio, 52-week range, beta, dividend yield, and other key financials.
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | Yes | Stock ticker symbol (e.g. 'AAPL', 'NVDA', 'MSFT') |
| Name | Required | Description | Default |
|---|---|---|---|
| stock | Yes | ||
| ticker | Yes | ||
| top_holders | Yes | ||
| position_basis | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "position_basis": {
+ "$ref": "#/properties/stock/properties/sector"
+ },
+ "stock": {
+ "additionalProperties": false,
+ "properties": {
+ "avg_volume": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "beta": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "current_price": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "dividend_yield_pct": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "eps": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "fifty_two_week_high": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "fifty_two_week_low": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "industry": {
+ "$ref": "#/properties/stock/properties/sector"
+ },
+ "market_cap": {
+ "anyOf": [
+ {
+ "pattern": "^-?\\d+(\\.\\d+)?([eE][-+]?\\d+)?$",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Exact decimal string as served by ko.io (not rounded); null = unknown"
+ },
+ "pe_ratio": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "previous_close": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "price_date": {
+ "$ref": "#/properties/stock/properties/sector"
+ },
+ "profit_margins": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "sector": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "sector",
+ "industry",
+ "market_cap",
+ "current_price",
+ "price_date",
+ "previous_close",
+ "fifty_two_week_high",
+ "fifty_two_week_low",
+ "pe_ratio",
+ "eps",
+ "beta",
+ "dividend_yield_pct",
+ "profit_margins",
+ "avg_volume"
+ ],
+ "type": "object"
+ },
+ "ticker": {
+ "type": "string"
+ },
+ "top_holders": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "call_shares": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "cik": {
+ "$ref": "#/properties/stock/properties/sector"
+ },
+ "equity_shares": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "has_option_legs": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "holding_value": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "name": {
+ "$ref": "#/properties/stock/properties/sector"
+ },
+ "portfolio_weight_pct": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "put_shares": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ },
+ "shares_held": {
+ "$ref": "#/properties/stock/properties/market_cap"
+ }
+ },
+ "required": [
+ "cik",
+ "name",
+ "shares_held",
+ "holding_value",
+ "portfolio_weight_pct",
+ "equity_shares",
+ "call_shares",
+ "put_shares",
+ "has_option_legs"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "ticker",
+ "stock",
+ "position_basis",
+ "top_holders"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that—no mention of data freshness, rate limits, or output behavior. It does not contradict the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that immediately states the action and resource, then lists the key return fields. There is no redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read-only tool with an output schema and comprehensive annotations, the description is largely sufficient. The only notable gap is the lack of sibling differentiation, but the low complexity and rich structured metadata compensate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the ticker parameter is already well documented with examples ('AAPL', 'NVDA', 'MSFT'). The description adds no additional parameter semantics, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource ('Get a company's profile') and enumerates concrete fields such as sector, market cap, P/E ratio, and 52-week range. It is clear and informative, though it does not explicitly distinguish itself from siblings like get_stock_price or get_stock_financials.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool is for retrieving a broad company profile snapshot, but it does not state when to prefer it over similar siblings or when not to use it. There is no explicit alternative routing or exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.