Skip to main content
Glama

Checking blockchain rankings

growth_chain_rank
Read-onlyIdempotent

Get chain growth rankings by active addresses, transactions, gas fees and DEX volume.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "growth_chain_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesGrowthChainRankRequest containing parameters and pagination settings

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
  2. Added
  3. Removed
  4. Changed6 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
      -  "ChainType": {
      -    "description": "Chain type options for growth ranking.",
      -    "enum": [
      -      "all",
      -      "evm"
      -    ],
      -    "type": "string"
      -  },
      -  "GrowthChainRankRequest": {
      -    "description": "Request for growth chain rank (flattened).",
      -    "properties": {
      -      "chain_type": {
      -        "$ref": "#/$defs/ChainType",
      -        "default": "all",
      -        "description": "Type of chains to include in growth analysis"
      -      },
      -      "time_frame": {
      -        "$ref": "#/$defs/GrowthTimeFrame",
      -        "default": "7",
      -        "description": "Time frame for growth analysis"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  "GrowthTimeFrame": {
      -    "description": "Time frames for growth chain ranking analysis.",
      -    "enum": [
      -      "7",
      -      "30",
      -      "365"
      -    ],
      -    "type": "string"
      -  }
      -}
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / request / $ref
      Removed value: -"#/$defs/GrowthChainRankRequest"
    • addedInput schema / properties / request / description
      Added value: +"GrowthChainRankRequest containing parameters and pagination settings"
    • addedInput schema / properties / request / properties
      Added value: +{
      +  "chain_type": {
      +    "default": "all",
      +    "description": "Type of chains to include in growth analysis",
      +    "enum": [
      +      "all",
      +      "evm"
      +    ],
      +    "type": "string"
      +  },
      +  "time_frame": {
      +    "default": "7",
      +    "description": "Time frame for growth analysis",
      +    "enum": [
      +      "7",
      +      "30",
      +      "365"
      +    ],
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / request / type
      Added value: +"object"
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the metric dimensions being ranked but says nothing about ordering, number of chains returned, or how "growth" is computed; with an output schema present, this is acceptable but thin.

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?

A single front-loaded sentence with zero filler or redundancy. It is efficient, though the brevity means no structure beyond the one clause.

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?

For a simple read-only tool with one nested request object, a fully documented schema, an output schema and complete annotations, the description supplies enough context to invoke it correctly. The remaining gap – ranking direction and result size – is plausibly covered by the output schema.

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% – both nested fields (chain_type, time_frame) carry enum values, defaults and descriptions. The description names no parameter, so it adds nothing beyond the schema; baseline 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?

States a specific verb and resource ("Get chain growth rankings") plus the four metrics the ranking is computed on, which is far more concrete than the tautological title. It does not explicitly contrast with the address-centric siblings, so differentiation must be inferred from the subject matter.

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 when-to-use guidance, no exclusions, and no named alternative or prerequisite. The only usage signal is implicit in the description's subject (chain-level growth) versus the address-level siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources