Skip to main content
Glama
longbridge

longbridge

Official

Institution Rating Industry Rank

institution_rating_industry_rank
Read-onlyIdempotent

Retrieve industry peers ranked by institutional analyst ratings, with pagination support for browsing. Use this to compare analyst sentiment across companies in the same sector.

Instructions

Get peers ranked by institution analyst ratings in the same industry. Paginated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sizeNoPage size (default: 20)
symbolYesSecurity symbol, e.g. "AAPL.US"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listNo
itemsNo

Schema Changelog

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

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"InstitutionRatingIndustryRankParam"
  2. Changed12 schema fields changedv0.6.0
    • removedOutput schema / $defs / InstitutionRatingIndustryRankItem / description
      Removed value: -"One peer in `institution_rating_industry_rank`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / InstitutionRatingIndustryRankItem / properties / buy_count / description
      Removed value: -"Buy rating count."
    • removedOutput schema / $defs / InstitutionRatingIndustryRankItem / properties / consensus_rating / description
      Removed value: -"Consensus rating label."
    • removedOutput schema / $defs / InstitutionRatingIndustryRankItem / properties / name / description
      Removed value: -"Display name."
    • removedOutput schema / $defs / InstitutionRatingIndustryRankItem / properties / sell_count / description
      Removed value: -"Sell rating count."
    • removedOutput schema / $defs / InstitutionRatingIndustryRankItem / properties / symbol / description
      Removed value: -"Security symbol (transformed from `counter_id`)."
    • removedOutput schema / $defs / InstitutionRatingIndustryRankItem / properties / target_price / description
      Removed value: -"Target price."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `institution_rating_industry_rank`. Peers ranked by analyst\nratings.\n\nThe tool description says `list[]`, while the implementation transforms a\ntop-level `items[]` array (rewriting `counter_id` → `symbol`). Both names\nare modelled so the schema matches whichever the upstream emits. Subset of\ndocumented fields; upstream may return more."
    • removedOutput schema / properties / items / description
      Removed value: -"Ranked peers (key the implementation transforms in place)."
    • removedOutput schema / properties / list / description
      Removed value: -"Ranked peers (description's documented key)."
    • removedOutput schema / title
      Removed value: -"InstitutionRatingIndustryRankResponse"
  3. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "InstitutionRatingIndustryRankItem": {
      +      "description": "One peer in `institution_rating_industry_rank`.\n\nSubset of documented fields; upstream may return more.",
      +      "properties": {
      +        "buy_count": {
      +          "description": "Buy rating count.",
      +          "format": "int64",
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "consensus_rating": {
      +          "description": "Consensus rating label.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "name": {
      +          "description": "Display name.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "sell_count": {
      +          "description": "Sell rating count.",
      +          "format": "int64",
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "symbol": {
      +          "description": "Security symbol (transformed from `counter_id`).",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "target_price": {
      +          "description": "Target price.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "description": "Returned by `institution_rating_industry_rank`. Peers ranked by analyst\nratings.\n\nThe tool description says `list[]`, while the implementation transforms a\ntop-level `items[]` array (rewriting `counter_id` → `symbol`). Both names\nare modelled so the schema matches whichever the upstream emits. Subset of\ndocumented fields; upstream may return more.",
      +  "properties": {
      +    "items": {
      +      "description": "Ranked peers (key the implementation transforms in place).",
      +      "items": {
      +        "$ref": "#/$defs/InstitutionRatingIndustryRankItem"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "list": {
      +      "description": "Ranked peers (description's documented key).",
      +      "items": {
      +        "$ref": "#/$defs/InstitutionRatingIndustryRankItem"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    }
      +  },
      +  "title": "InstitutionRatingIndustryRankResponse",
      +  "type": "object"
      +}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. Addedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, confirming it is a safe read operation. The description adds 'Paginated', which is a behavioral trait not covered by annotations. However, other aspects like error handling or rate limits are not disclosed.

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, consisting of two short sentences that immediately convey the core functionality. Every word is necessary, and the structure is front-loaded without any fluff.

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

Completeness4/5

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

Given the presence of annotations, a full input schema, and an output schema, the description is mostly complete. It explains the tool's purpose and pagination, but could be slightly more explicit about the ranking order or what constitutes 'in the same industry'.

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 coverage is 100% with clear descriptions for all three parameters (page, size, symbol). The description does not add any additional meaning or constraints beyond what the schema provides, aligning with the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'get' and the resource 'peers ranked by institution analyst ratings in the same industry'. It distinguishes itself from sibling tools like 'industry_peers' and 'institution_rating' by combining both concepts, and mentions pagination.

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 provide any guidance on when to use this tool versus alternatives such as 'industry_peers' or 'institution_rating'. No exclusions or context for selection are given.

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