Skip to main content
Glama
BACH-AI-Tools

Finmap MCP Server

Company profile (US)

get_company_profile

Retrieve business description, industry classification, and company background for US-listed companies by specifying exchange and ticker symbol.

Instructions

Get business description, industry, and background for a US-listed company by ticker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exchangeYesUS exchange: amex, nasdaq, nyse
tickerYesStock ticker symbol (case-sensitive)

Implementation Reference

  • src/core.ts:778-803 (registration)
    Registration of the 'get_company_profile' tool, including input schema and inline handler function
    server.registerTool(
    	"get_company_profile",
    	{
    		title: "Company profile (US)",
    		description:
    			"Get business description, industry, and background for a US-listed company by ticker.",
    		inputSchema: {
    			exchange: z
    				.enum(US_EXCHANGES)
    				.describe("US exchange: amex, nasdaq, nyse"),
    			ticker: z.string().describe("Stock ticker symbol (case-sensitive)"),
    		},
    	},
    	async ({ exchange, ticker }: { exchange: USExchange; ticker: string }) => {
    		try {
    			const securityInfo = await fetchSecurityInfo(exchange, ticker);
    			return createResponse({
    				info: INFO,
    				charts: createCharts(exchange),
    				...securityInfo,
    			});
    		} catch (error) {
    			return createErrorResponse(error);
    		}
    	},
    );
  • Inline handler that fetches company profile data via fetchSecurityInfo and formats the response
    async ({ exchange, ticker }: { exchange: USExchange; ticker: string }) => {
    	try {
    		const securityInfo = await fetchSecurityInfo(exchange, ticker);
    		return createResponse({
    			info: INFO,
    			charts: createCharts(exchange),
    			...securityInfo,
    		});
    	} catch (error) {
    		return createErrorResponse(error);
    	}
    },
  • Helper function that fetches the detailed company profile JSON data from the GitHub repository based on exchange and ticker
    async function fetchSecurityInfo(
    	exchange: USExchange,
    	ticker: string,
    ): Promise<Record<string, any>> {
    	const firstLetter = ticker.charAt(0).toUpperCase();
    	const url = `${DATA_BASE_URL}/data-us/refs/heads/main/securities/${exchange}/${firstLetter}/${ticker}.json`;
    
    	const response = await fetch(url);
    	if (response.status === 404) {
    		throw new Error(`Security ${ticker} not found on ${exchange}`);
    	}
    
    	const data = (await response.json()) as any;
    	return data;
    }
  • Type definition for US exchanges used in the tool's input schema
    const US_EXCHANGES = ["amex", "nasdaq", "nyse"] as const;
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a 'Get' operation, implying read-only behavior, but doesn't disclose other traits like rate limits, authentication needs, error handling, or what happens if the ticker is invalid. For a tool with no annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the purpose ('Get business description, industry, and background') and specifies scope ('for a US-listed company by ticker'). There is no wasted text, and every word contributes to clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 required parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the purpose and scope well, but lacks behavioral details (e.g., error cases, return format) and usage guidelines versus siblings. Without annotations or output schema, more context would be helpful for an agent.

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 100%, with both parameters well-documented in the schema (exchange with enum values and ticker as case-sensitive). The description adds no additional parameter semantics beyond implying the ticker is for US-listed companies, which is already covered by the schema's exchange enum. Baseline 3 is appropriate when the schema does the heavy lifting.

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 description clearly states the action ('Get'), the target resource ('business description, industry, and background'), and the scope ('for a US-listed company by ticker'). It distinguishes itself from siblings like get_stock_data (which likely provides financial metrics) or search_companies (which likely searches by name rather than retrieving by ticker).

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

Usage Guidelines3/5

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

The description implies usage by specifying 'US-listed company by ticker,' which suggests it's for retrieving profile data rather than market data (vs. get_stock_data) or searching (vs. search_companies). However, it lacks explicit guidance on when to use this tool versus alternatives like get_market_overview or list_tickers, and doesn't mention prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bach-finmap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server