Skip to main content
Glama

Companies

akkru_companies
Read-onlyIdempotent

Find a company and see what is covered for it.

  • search: companies whose name contains query, or whose ticker or registrant id starts with it; up to 8 candidates, best match first. 10 credits.

  • lookup: one company by exactly one of ticker, cik, dart_corp_code, edinet_code, lei or uscc: its identity, every ticker it has traded under, links to its filings lists, and the forms, fiscal years and quarters on file. 8 credits, also when no company matches.

  • list: every company covered, 100 per page; jurisdiction filters by market. 30 credits per page. Results stop at your plan's coverage. On Pro plans and above, search and list also give each company's industry classification.

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": {
      "action": "<action>"
    },
    "name": "akkru_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNo(lookup) SEC CIK, digits, e.g. "320193" (companies filing with the SEC).
leiNo(lookup) Legal Entity Identifier, 20 characters (European filers).
pageNo(list) Page number, from 1; the response's next_page gives the next one.
usccNo(lookup) Unified Social Credit Code, 18 characters (China A-share companies).
queryNo(search) Name, ticker or registrant id to search for (1-64 characters); English names only.
actionYesWhat to do; each action is described in the tool description.
detailNoResponse detail, same price at every level: "full" (default) returns everything; "light" leaves out the bulkiest fields, such as breakdown lists; "minimal" returns only the values and what identifies them, without sources or calculation details. Every action takes it; a call without detail levels ignores it. Try "light" or "minimal" for shorter replies that use less context and fewer tokens.
tickerNo(lookup) Ticker, e.g. "AAPL", "000100", "1332", "VIRI_F", "600519_CN"; any symbol the company has traded under.
page_sizeNo(list) Companies per page, 1-100 (default 100).
as_of_dateNo(lookup) Date "YYYY-MM-DD" (not in the future): only what had been filed by that day counts. Default: no cutoff.
edinet_codeNo(lookup) Japanese EDINET code, e.g. "E02778".
jurisdictionNo(search, list) Market: "US", "KR", "JP", "EU", "CN", or "all" (default: every market your plan covers).
dart_corp_codeNo(lookup) Korean DART corp code, 8 digits, e.g. "00126380".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as_of_date
      Added value: +{
      +  "description": "(lookup) Date \"YYYY-MM-DD\" (not in the future): only what had been filed by that day counts. Default: no cutoff.",
      +  "format": "date",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the non-obvious economics and limits: 10 credits for search, 8 for lookup 'also when no company matches', 30 credits per page for list, results truncated at the plan's coverage, and industry classification only on Pro and above. Billing-on-empty-result and plan gating are exactly the behaviors an agent could not infer from annotations or schema.

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?

One framing sentence followed by three labeled bullets, each front-loading the action name and appending cost — the highest-value facts in the smallest space for a 13-parameter, three-action tool. No sentence is redundant with the title or with the structured fields.

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 13 parameters, the description carries return-value burden well: lookup is described as returning identity, all historical tickers, filing-list links, and forms/fiscal years/quarters on file, and list returns 100 per page. It never states what a search candidate records contain beyond industry classification, a small gap for the search action.

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 cross-parameter constraints the schema cannot express: lookup requires 'exactly one of' the six identifier fields, search matches name-contains versus ticker/registrant-id prefix, and the 8-candidate best-match-first ordering. It does not add format details for identifiers, but the schema already covers those.

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?

Names the resource (companies) and enumerates three distinct verbs — search, lookup, list — with a precise scope for each: 'companies whose name contains query, or whose ticker or registrant id starts with it' versus 'one company by exactly one of ticker, cik, ...'. This is specific enough that an agent can pick the right action without opening the schema, and the identity/lookup semantics distinguish it from sibling tools like akkru_filings.

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

Usage Guidelines4/5

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

The bullets give clear per-action selection context (find a company, resolve one entity, enumerate coverage) plus a concrete narrowing rule via jurisdiction. It does not explicitly route the agent to sibling tools (e.g. akkru_filings for the filing lists this returns links to), so there is no stated when-not or alternatives clause, keeping it below a 5.

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