divux

Company: registry record, complaints and SEC filings

check_company

Read-only

Returns, for a company outside the US, whether it is in the global LEI register (GLEIF): legal name, country, local registry number, whether it is active and its ultimate parent. For a US company, returns the Consumer Financial Protection Bureau complaint record (counts, top problems, on-time answers, how often people got relief) and whether it is an FDIC-insured bank, and for a public company what it reported to the SEC (EDGAR XBRL): revenue, net income and diluted EPS for four fiscal years, the latest quarter against a year earlier, cash and shares outstanding, additional annual financial metrics, up to eight reported quarters, company profile and recent filings. The input is a name or a US ticker such as NVDA. Complaint counts grow with company size. Applies to questions about what public records show about a company. Not investment advice. Stock prices are not included.

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": {
      "company": "<company>"
    },
    "name": "check_company"
  }
}

Input Schema

Name	Required	Description
`months`	No	How far back to count; default 24
`company`	Yes	Company name or US stock ticker, e.g. 'Capital One', 'Chime', 'NVDA'
`country`	No	Country where the company is registered or operates; leave out for the US

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / company / description

Previous value: -"Company name, e.g. 'Rocket Mortgage', 'Capital One', 'Chime'"New value: +"Company name or US stock ticker, e.g. 'Capital One', 'Chime', 'NVDA'"

changedInput schema / properties / company / minLength
```
Previous value: -2New value: +1
```

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / country

Added value: +{
+  "description": "Country where the company is registered or operates; leave out for the US",
+  "maxLength": 60,
+  "type": "string"
+}

AddedOct 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint/openWorldHint already declaring the safety profile, the description adds real behavioral context: it discloses the three upstream sources, that the response shape branches on country and on public-vs-private status, and that complaint counts scale with company size (a signal about interpreting magnitudes). It does not mention latency, rate limits, or partial-data/failure behavior when a company isn't found.

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

Conciseness3/5

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

The purpose and exclusions are front-loaded and there is no filler sentence, but the middle is a single sprawling enumeration of every returned field, forcing the reader to parse one very long multi-clause sentence. The return-value inventory could be tightened or bulleted without losing information.

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 complex multi-source tool with no output schema, the description is unusually complete: it tells the agent what data comes back in each branch and how to supply the input. The remaining gaps are modest, chiefly the months lookback parameter and what happens when no match is found.

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 3-baseline applies, and the description goes slightly beyond it by defining the input form (name or US ticker like NVDA) and the semantics of country ("leave out for the US" is the deciding switch between the two response modes). The months window parameter that governs complaint counting is never mentioned in the description.

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 concrete verb and resource: it returns public-record facts about a company, split by jurisdiction (GLEIF LEI register for non-US, CFPB complaints plus FDIC and SEC EDGAR XBRL for US) with the exact fields named. That specificity makes it trivially distinguishable from domain siblings such as check_car, check_food or check_inflation.

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?

Gives a clear usage frame ("Applies to questions about what public records show about a company") and two explicit exclusions ("Not investment advice", "Stock prices are not included"), which nicely bound expectations. It does not name a sibling or an alternative for out-of-scope questions, so it falls short of full when-not/alternative guidance.

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

All divux tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?