operatingRetrieve company operating metrics for Hong Kong-listed stocks, including key business performance indicators.
Get company operating metrics (HK stocks only).
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Security symbol, e.g. "700.HK" |
| Name | Required | Description | Default |
|---|---|---|---|
| items | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.7.1Input schema / titleRemoved value: -"SymbolParam"v0.6.0Output schema / $defs / OperatingItem / descriptionRemoved value: -"One record in `operating`'s `items`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / OperatingItem / properties / metric_name / descriptionRemoved value: -"Metric name (e.g. passenger traffic, cargo volume)."Output schema / $defs / OperatingItem / properties / period / descriptionRemoved value: -"Reporting period."Output schema / $defs / OperatingItem / properties / unit / descriptionRemoved value: -"Unit of measure."Output schema / $defs / OperatingItem / properties / value / descriptionRemoved value: -"Metric value."Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved value: -"Returned by `operating`. Wraps an `items` array of operating metrics\n(HK stocks only).\n\nSubset of documented fields; upstream may return more."Output schema / properties / items / descriptionRemoved value: -"Operating metric records."Output schema / titleRemoved value: -"OperatingResponse"v0.5.6Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "OperatingItem": {
+ "description": "One record in `operating`'s `items`.\n\nSubset of documented fields; upstream may return more.",
+ "properties": {
+ "metric_name": {
+ "description": "Metric name (e.g. passenger traffic, cargo volume).",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "period": {
+ "description": "Reporting period.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "unit": {
+ "description": "Unit of measure.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "value": {
+ "description": "Metric value.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ }
+ },
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "description": "Returned by `operating`. Wraps an `items` array of operating metrics\n(HK stocks only).\n\nSubset of documented fields; upstream may return more.",
+ "properties": {
+ "items": {
+ "description": "Operating metric records.",
+ "items": {
+ "$ref": "#/$defs/OperatingItem"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ }
+ },
+ "title": "OperatingResponse",
+ "type": "object"
+}v0.4.5v0.4.0v0.3.2v0.3.1v0.1.12Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint, idempotentHint, and non-destructive behavior. The description adds no further behavioral context beyond confirming it is a read operation. It does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence that is front-loaded with the action and resource, followed by the scope constraint. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is adequate for a simple, one-parameter read tool with an existing output schema. It does not detail the specific metrics returned, but the output schema covers that. Slight improvement could be mentioning the type of operating metrics (e.g., revenue, profit).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides a 100% description coverage for the only parameter 'symbol' with an example. The description adds no additional meaning beyond what the schema already conveys, meriting the baseline score.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get'), the resource ('company operating metrics'), and the scope ('HK stocks only'), making it distinct from sibling tools that cover other metrics or markets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states the stock market restriction ('HK stocks only'), which guides when to use this tool. However, it does not mention alternatives for non-HK stocks or provide explicit when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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