Skip to main content
Glama

FinanceQuery

Company Profile

get_company_profile
Read-onlyIdempotent

Get a company's identity/classification profile (name, description, asset type, exchange, currency, country, sector, industry, market capitalization).

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": "get_company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesStock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and idempotency profile is covered without the description's help. The description contributes the content scope by listing which attributes come back, but says nothing about behavior the annotations miss, such as what happens with an invalid or delisted ticker, whether the response is cached or live, or any rate limits. Given annotation coverage, a 3 is fair.

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?

A single sentence with the verb and resource front-loaded, and the parenthetical list is dense but useful for scoping the response. Nothing is redundant with the title, though the long inline enumeration slightly hurts scannability.

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?

For a two-parameter read-only lookup with no output schema, the description is nearly sufficient: it enumerates the returned attributes, which substitutes for the missing output schema. The remaining gap is routing guidance against the many sibling 'get_*' tools, which an agent would need in order to pick this one confidently.

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 'symbol' documented as the stock ticker and 'fields' documented as a comma-separated GraphQL field list where omission means all fields. The description's parenthetical field list loosely corresponds to the 'fields' parameter but adds no syntax, valid-value, or defaulting detail beyond the schema. Baseline 3 applies when the schema carries the semantics.

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?

The description names a specific verb (get) and resource (company's identity/classification profile), then enumerates the fields returned (name, asset type, exchange, sector, industry, market cap). That enumeration makes clear it is a static descriptive profile rather than pricing or financial-statement data, which implicitly separates it from siblings like get_financials. It does not explicitly name get_etf_profile as the contrasting tool for fund vehicles, so it falls short of a 5.

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 explicit when-to-use statement, no prerequisites, and no mention of an alternative tool. An agent must infer from the field list that this is the right call for entity classification and the wrong call for quotes, fundamentals, or ETF/fund metadata. That inference is reasonable but entirely unstated.

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.