Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaRelated ServersScoreDiscussions(1)
Rust
Hybrid

Executive

executive
Read-onlyIdempotent

Get company leadership and board member information using a security symbol. Access names, titles, and profiles for US and HK stocks.

Instructions

Get company executive and board member information.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
membersNo

Schema Changelog

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

  1. Changed1 schema field changedv0.8.7
    • addedOutput schema / $defs / ExecutiveMember / properties / title
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  3. Changed11 schema fields changedv0.6.0
    • removedOutput schema / $defs / ExecutiveMember / description
      Removed value: -"One person in `executive`'s `members`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / ExecutiveMember / properties / age / description
      Removed value: -"Age."
    • removedOutput schema / $defs / ExecutiveMember / properties / appointed_date / description
      Removed value: -"Date appointed."
    • removedOutput schema / $defs / ExecutiveMember / properties / biography / description
      Removed value: -"Biography."
    • removedOutput schema / $defs / ExecutiveMember / properties / compensation / description
      Removed value: -"Compensation."
    • removedOutput schema / $defs / ExecutiveMember / properties / name / description
      Removed value: -"Full name."
    • removedOutput schema / $defs / ExecutiveMember / properties / title
      Removed value: -{
-  "description": "Title / role.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `executive`. Wraps a `members` array of executives / board\nmembers.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / members / description
      Removed value: -"Executive and board members."
    • removedOutput schema / title
      Removed value: -"ExecutiveResponse"
  4. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "ExecutiveMember": {
+      "description": "One person in `executive`'s `members`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "age": {
+          "description": "Age.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "appointed_date": {
+          "description": "Date appointed.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "biography": {
+          "description": "Biography.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "compensation": {
+          "description": "Compensation.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Full name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "title": {
+          "description": "Title / role.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `executive`. Wraps a `members` array of executives / board\nmembers.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "members": {
+      "description": "Executive and board members.",
+      "items": {
+        "$ref": "#/$defs/ExecutiveMember"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "ExecutiveResponse",
+  "type": "object"
+}
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, and the description is consistent with these. However, it adds no context beyond the resource being fetched, such as whether the data pertains to a specific market or time period.

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 a single, concise sentence that front-loads the core purpose without redundancy. It contains no filler or unnecessary words.

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

Completeness3/5

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

The tool is simple with one fully documented parameter, annotations covering safety, and an output schema present. However, the description lacks usage guidance and does not differentiate from closely related sibling tools, leaving minor gaps in contextual completeness.

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 input schema already provides a full description of the 'symbol' parameter with an example ('700.HK'), and the description does not add any additional parameter semantics. With 100% schema coverage, the description adds no extra value here.

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 states a specific verb ('Get') and resource ('company executive and board member information'), clearly indicating the tool's function. However, it does not distinguish this from sibling tools like 'participants' or 'shareholder', which might also provide related corporate information.

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 or which alternatives might be more appropriate. It simply states what it retrieves without any context or exclusions, leaving the agent to infer the tool's applicability.

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