Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Company Profile

company
Read-onlyIdempotent

Retrieve an overview for a given security symbol, including market cap, top rank tags, and share list. Supports US and HK market response formats.

Instructions

Get company overview. US accounts querying a .US symbol get a differently-shaped response not matching output_schema (intro, market_cap, top_rank_tags, sharelist, detail_url); other combinations match output_schema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSecurity symbol, e.g. "700.HK"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ceoNo
nameNo
introNo
websiteNo
exchangeNo
industryNo
employeesNo
ccy_symbolNo
detail_urlNo
market_capNo
share_listNo
descriptionNo
founded_yearNo
top_rank_tagsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.8.7
    • addedOutput schema / properties / description
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed5 schema fields changedv0.8.4
    • 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"
+  ]
+}
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. Changed12 schema fields changedv0.6.0
    • 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"
  5. Changed1 schema field changedv0.5.6
    • 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"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context by warning that responses for US accounts querying .US symbols will not match the output schema, which is valuable for an agent to anticipate.

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?

The description is extremely concise and front-loaded. The first sentence states the core purpose, and the second sentence adds a valuable edge-case warning without unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with one well-documented parameter and an output schema, the description covers the main function and the notable exception. No significant gaps remain given the structured annotations and schema.

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?

The schema covers the single parameter 'symbol' with a description and example, so the description need not add much. The description does not provide additional parameter semantics beyond what the schema already offers, which is acceptable at the baseline.

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 clearly states the function as 'Get company overview' with a specific verb and resource. However, it does not explicitly differentiate this tool from sibling tools like static_info or quote, aside from the implied subject matter.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It only mentions a special case for US accounts querying .US symbols, but does not clarify broader scenarios or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server