Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Rank Categories

rank_categories
Read-onlyIdempotent

Retrieve rank tab category configurations for the popularity leaderboard, providing the second_tags keys needed to query rank_list.

Instructions

Get rank tab category configurations for the popularity leaderboard. Pass a second_tags key (e.g. hot_all-us) to rank_list.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "RankFirstTag": {
-      "properties": {
-        "key": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "second_tags": {
-          "items": {
-            "$ref": "#/$defs/RankSecondTag"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "RankSecondTag": {
-      "properties": {
-        "key": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "market": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "first_tags": {
-      "items": {
-        "$ref": "#/$defs/RankFirstTag"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed10 schema fields changedv0.6.0
    • removedOutput schema / $defs / RankFirstTag / properties / key / description
      Removed value: -"Category key."
    • removedOutput schema / $defs / RankFirstTag / properties / name / description
      Removed value: -"Display name."
    • removedOutput schema / $defs / RankFirstTag / properties / second_tags / description
      Removed value: -"Sub-categories. Pass a `second_tags[].key` to `rank_list`."
    • removedOutput schema / $defs / RankSecondTag / properties / key / description
      Removed value: -"Tab key to pass to `rank_list` (e.g. \"hot_all-us\")."
    • removedOutput schema / $defs / RankSecondTag / properties / market / description
      Removed value: -"Market this tab covers, e.g. \"US\" / \"HK\"."
    • removedOutput schema / $defs / RankSecondTag / properties / name / description
      Removed value: -"Display name."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `rank_categories`. Wraps a `first_tags` array of rank tab\ncategory configurations for the popularity leaderboard. Subset of the wire\nresponse."
    • removedOutput schema / properties / first_tags / description
      Removed value: -"Top-level rank category tags."
    • removedOutput schema / title
      Removed value: -"RankCategoriesResponse"
  4. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "RankFirstTag": {
+      "properties": {
+        "key": {
+          "description": "Category key.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Display name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "second_tags": {
+          "description": "Sub-categories. Pass a `second_tags[].key` to `rank_list`.",
+          "items": {
+            "$ref": "#/$defs/RankSecondTag"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "RankSecondTag": {
+      "properties": {
+        "key": {
+          "description": "Tab key to pass to `rank_list` (e.g. \"hot_all-us\").",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "market": {
+          "description": "Market this tab covers, e.g. \"US\" / \"HK\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Display name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `rank_categories`. Wraps a `first_tags` array of rank tab\ncategory configurations for the popularity leaderboard. Subset of the wire\nresponse.",
+  "properties": {
+    "first_tags": {
+      "description": "Top-level rank category tags.",
+      "items": {
+        "$ref": "#/$defs/RankFirstTag"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "RankCategoriesResponse",
+  "type": "object"
+}
  5. Addedv0.4.5

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds minimal behavioral context beyond the basic purpose; it does not disclose any side effects or special handling. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is concise and clear, but the second sentence introduces a note about rank_list that seems misplaced or ambiguous, undermining overall structure. It is short but not entirely focused on this tool's own usage.

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?

For a read-only tool with no required parameters and no output schema, the description gives the basic purpose but leaves the nature of 'rank tab category configurations' vague. It does not explain how the returned data might be used or how it relates to rank_list, leaving some gap in practical guidance.

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 only parameter _jq is fully described in the schema (100% coverage). The description adds no extra meaning about parameters, 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 first sentence clearly states the tool fetches 'rank tab category configurations for the popularity leaderboard,' providing a specific verb and resource. It does not explicitly contrast with the sibling rank_list, but the distinct noun 'categories' and the leaderboard context help differentiate it.

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 does not say when to use this tool versus alternatives. The second sentence instructs passing a 'second_tags key' to rank_list, which seems to reference a different tool and could be a workflow hint, but it is not framed as usage guidance for this tool. No exclusions or alternative conditions are given.

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