longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Company Profile

company

Read-onlyIdempotent

Get an overview for a security symbol. For US symbols, includes market cap, top rank tags, share list, and detail URL, with region detected from your account.

Instructions

Get company overview. US accounts querying a .US symbol get a US-specific variant (intro, market_cap, top_rank_tags, sharelist, detail_url). The region is detected from the account automatically.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_jq`	No	Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data \| map({symbol}). Omit for the full response.
`symbol`	Yes	Security symbol, e.g. "700.HK". Use the canonical form — a padded code like "00700.HK" returns an empty record, not an error.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.12.0Sep 23, 2026

addedInput schema / properties / _jq / description

Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."

changedInput schema / properties / symbol / description

Previous value: -"Security symbol, e.g. \"700.HK\""New value: +"Security symbol, e.g. \"700.HK\". Use the canonical form — a padded code like \"00700.HK\" returns an empty record, not an error."

Changed2 schema fields changedv0.10.6Sep 10, 2026

addedInput schema / properties / _jq
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "ccy_symbol": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "ceo": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "description": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "detail_url": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "employees": {
-      "format": "int64",
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "exchange": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "founded_year": {
-      "format": "int64",
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "industry": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "intro": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "market_cap": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "share_list": {
-      "items": true,
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "top_rank_tags": {
-      "items": true,
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "website": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.8.7Aug 19, 2026
- addedOutput schema / properties / description
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed5 schema fields changedv0.8.4Jul 25, 2026

addedOutput schema / properties / ccy_symbol

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / detail_url

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / intro

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / share_list

Added value: +{
+  "items": true,
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / top_rank_tags

Added value: +{
+  "items": true,
+  "type": [
+    "array",
+    "null"
+  ]
+}

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SymbolParam"
```

Changed12 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / description

Removed value: -"Returned by `company`. Company overview / profile.\n\nSubset of documented fields; upstream may return more."

removedOutput schema / properties / ceo / description
```
Removed value: -"Chief Executive Officer."
```

removedOutput schema / properties / description

Removed value: -{
-  "description": "Business profile / description.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / employees / description
```
Removed value: -"Number of employees."
```
removedOutput schema / properties / exchange / description
```
Removed value: -"Listing exchange."
```
removedOutput schema / properties / founded_year / description
```
Removed value: -"Year the company was founded."
```
removedOutput schema / properties / industry / description
```
Removed value: -"Industry classification."
```
removedOutput schema / properties / market_cap / description
```
Removed value: -"Market capitalization."
```
removedOutput schema / properties / name / description
```
Removed value: -"Company name."
```
removedOutput schema / properties / website / description
```
Removed value: -"Company website."
```
removedOutput schema / title
```
Removed value: -"CompanyResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `company`. Company overview / profile.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "ceo": {
+      "description": "Chief Executive Officer.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "Business profile / description.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "employees": {
+      "description": "Number of employees.",
+      "format": "int64",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "exchange": {
+      "description": "Listing exchange.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "founded_year": {
+      "description": "Year the company was founded.",
+      "format": "int64",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "industry": {
+      "description": "Industry classification.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "market_cap": {
+      "description": "Market capitalization.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Company name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "website": {
+      "description": "Company website.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "CompanyResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already signal read-only, idempotent, and non-destructive behavior. The description adds non-obvious behavioral context: US accounts querying .US symbols receive a different variant with listed fields, and region detection is automatic.

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?

Three short sentences with no filler: the first states the purpose, the second captures the key US-specific variant, and the third clarifies the trigger. Information is front-loaded and every sentence earns its place.

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 simple read-only overview with fully documented parameters and strong annotations, the description covers the essential purpose and a significant output-variation case. The lack of an explicit return-structure description is a minor gap, not a blocking one.

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%, so both _jq and symbol are already fully documented, including the canonical-form caveat for symbols. The description adds no parameter-specific meaning, so the baseline of 3 applies.

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 opens with a clear verb and object: 'Get company overview.' It is specific enough to identify the tool's core purpose, though it does not explicitly distinguish itself from siblings like static_info or security_facts.

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?

The description implies when to use the tool through 'Get company overview,' but it never states explicit use cases, exclusions, or alternatives. The US-account/.US variant note is practical output guidance, not tool-selection guidance.

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

Deploy Server

Company Profile

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools