Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Executive

executive
Read-onlyIdempotent

Retrieve company board members and leadership information for a given security symbol. Input the symbol to get details for US/HK markets.

Instructions

Get company executive and board member information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional 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.
symbolYesSecurity 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.

  1. Changed2 schema fields changedv0.12.0
    • 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."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "ExecutiveMember": {
-      "properties": {
-        "age": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "appointed_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "biography": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "compensation": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "title": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "members": {
-      "items": {
-        "$ref": "#/$defs/ExecutiveMember"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.8.7
    • addedOutput schema / $defs / ExecutiveMember / properties / title
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  5. 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"
  6. 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"
+}
  7. Addedv0.4.5
  8. Removedv0.4.0
  9. Addedv0.3.2
  10. Removedv0.3.1
  11. First observedv0.1.12

TDQS

B3.2/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, so the safety profile is covered. The description adds the data scope (executives and board members) but no further behavioral details such as response shape, pagination, or rate limits. This is adequate but not rich.

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?

The description is a single, front-loaded sentence with no wasted words. It is appropriately sized for a simple read tool, though it lacks the additional routing value seen in higher-scoring definitions.

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?

Given low complexity, complete parameter schema, and strong annotations, the description is minimally sufficient. Still, with no output schema and no usage guidance, the agent gets only a broad sense of what is returned and no help choosing this tool among many siblings.

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 the schema fully documents both 'symbol' and '_jq', including the canonical symbol caveat. The description itself adds no parameter detail, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Get company executive and board member information.' It is not a tautology and clearly identifies what data the tool returns. However, it does not differentiate itself from sibling tools such as 'participants' or 'company', so it misses the top score.

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?

There is no guidance on when to use this tool versus alternatives, and no mention of prerequisites or exclusions. The description only states what the tool does, leaving the agent to infer usage from the tool name and context.

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

Deploy Server

Other Tools