Skip to main content
Glama

get_company

Find a company by CIK, ticker or part of its name. One match returns its card (industry, state, tickers, first annual report), its offerings with labels and statuses, and its latest 50 filings; several matches return the list.

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": {
      "query": "<query>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYese.g. 'AAPL', '320193', 'Lycia Therapeutics'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full disclosure burden and does well: it explains the two distinct return modes (single match returns a card plus offerings plus latest 50 filings; multiple matches return a list). It omits no-match/error behavior and any auth or rate-limit context, which keeps it short of a 5.

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?

A single compact sentence that front-loads the lookup then the two return branches. Every clause earns its place; nothing is redundant.

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 one-parameter read tool with no output schema, the description covers return values well enough to set expectations. The remaining gap is failure/no-match behavior, which matters for a partial-name search that may return zero results.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the query may be a CIK, a ticker, or part of a name. That is the key disambiguation an agent needs to construct a valid query.

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 ('Find') plus the resource ('a company') and the accepted identifiers (CIK, ticker, partial name). An agent can immediately tell this is the company-lookup tool and distinguish it from list_offerings, search_filings, get_stats, and explain_form.

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?

Usage is implied by the identifier formats it accepts, and no sibling overlaps meaningfully, but the description never explicitly says when to use it versus alternatives such as list_offerings for a known company's offerings.

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.

Resources