Skip to main content
Glama

Drillr — The financial MCP for AI agents

by ai.drillr
OverviewDiscussionsAdmin

company_search

Read-only

Use for qualitative company discovery (industry, business model, supply chain, competitors, management background). For numerical screening (revenue, margins, ratios, growth rates) use run_sql on company_snapshot instead.

Drillr's company knowledge graph — searchable across industry classification, product offerings, business model, segment structure, competitive landscape, supply chain, management background, and customer profile.

Coverage: US, Japan, Hong Kong, China A-shares, and Korea. market accepts one lowercase value or a list from us | jp | hk | cn | kr; omit it or pass [] for all five. List order does not set priority.

Pass a natural-language description (for example, "Hong Kong and China EV battery suppliers"). Returns a structured list of matching companies with context snippets.

ONLY for finding a LIST of companies by description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural-language company description
marketNoOptional market filter. Pass one lowercase value or a list from 'us' | 'jp' | 'hk' | 'cn' | 'kr'. Omit or pass [] for all five; list order does not set priority.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / market / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "us",
-      "jp",
-      "hk",
-      "cn"
-    ],
-    "type": "string"
-  },
-  {
-    "items": {
-      "$ref": "#/properties/market/anyOf/0"
-    },
-    "maxItems": 4,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "enum": [
+      "us",
+      "jp",
+      "hk",
+      "cn",
+      "kr"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "$ref": "#/properties/market/anyOf/0"
+    },
+    "maxItems": 5,
+    "type": "array"
+  }
+]
    • changedInput schema / properties / market / description
      Previous value: -"Optional market filter. Pass one lowercase value or a list from 'us' | 'jp' | 'hk' | 'cn'. Omit or pass [] for all four; list order does not set priority."New value: +"Optional market filter. Pass one lowercase value or a list from 'us' | 'jp' | 'hk' | 'cn' | 'kr'. Omit or pass [] for all five; list order does not set priority."
  2. Changed6 schema fields changed
    • addedInput schema / properties / market / anyOf
      Added value: +[
+  {
+    "enum": [
+      "us",
+      "jp",
+      "hk",
+      "cn"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "$ref": "#/properties/market/anyOf/0"
+    },
+    "maxItems": 4,
+    "type": "array"
+  }
+]
    • changedInput schema / properties / market / description
      Previous value: -"Optional market filter: 'us' | 'jp' — the knowledge base covers US + Japan companies only. Omit to search both."New value: +"Optional market filter. Pass one lowercase value or a list from 'us' | 'jp' | 'hk' | 'cn'. Omit or pass [] for all four; list order does not set priority."
    • removedInput schema / properties / market / enum
      Removed value: -[
-  "us",
-  "jp"
-]
    • removedInput schema / properties / market / type
      Removed value: -"string"
    • changedInput schema / properties / query / description
      Previous value: -"natural language query"New value: +"Natural-language company description"
    • addedInput schema / properties / query / minLength
      Added value: +1
  3. Changed1 schema field changed
    • addedInput schema / properties / market
      Added value: +{
+  "description": "Optional market filter: 'us' | 'jp' — the knowledge base covers US + Japan companies only. Omit to search both.",
+  "enum": [
+    "us",
+    "jp"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark it read-only and non-destructive; the description adds meaningful behavior: returns a structured list with context snippets, accepts natural-language queries, covers exactly five markets, and clarifies that list order carries no priority. This complements the annotations without contradicting them.

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?

Information is front-loaded with the most important usage distinction first, and each paragraph has a clear role. Some redundancy exists between the first and second paragraphs' lists of qualitative dimensions, but the structure is still easy to scan and not bloated.

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, the description compensates by specifying the return shape as a structured list with context snippets. It covers input format, market enumeration, coverage, and scope, which is sufficient for a two-parameter discovery tool; only minor output-field detail is missing.

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; the description adds a concrete query example and expands the meaning of the market filter with coverage context and the 'omit or [] for all five' rule. Most market details repeat the schema, but the example and qualitative framing provide extra value.

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 opens with a specific verb and resource: qualitative company discovery across named dimensions, and closes with a constraint that it is ONLY for finding a list of companies by description. It also distinguishes itself from run_sql's numerical screening, making the tool's identity unambiguous even without an explicit title.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool (qualitative discovery) and when not to (numerical screening), naming run_sql on company_snapshot as the alternative. The final line 'ONLY for finding a LIST of companies by description' provides a hard boundary.

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

All Drillr — The financial MCP for AI agents toolsInspect
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