Skip to main content
Glama
Sign In
@blockchainacademics/mcp

@blockchainacademics/mcp

Official
by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_l2_comparison

Compare major L2 blockchains side-by-side including Base, Arbitrum, Optimism, zkSync, and others to choose the right scaling solution.

Instructions

L2 side-by-side: Base, Arbitrum, Optimism, zkSync, Starknet, Linea, Scroll, Mantle, Blast.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_l2_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.6/5.0
Behavior1/5

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

With no annotations provided, the description must disclose behavioral traits. It only lists the L2s compared, with no information about data freshness, mutability, authentication needs, or any side effects. For a data retrieval tool, this is insufficient.

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 description is a single, concise line. However, it is overly brief and lacks structure (e.g., no bullet points or clear separation of purpose and output). It earns its place but could be improved.

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

Completeness2/5

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

Given 0 parameters, no output schema, and no annotations, the description is the only source of context. It fails to specify what the comparison includes (e.g., TVL, fees, transactions) or how to interpret results. This is incomplete for a data tool.

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 input schema is empty (0 parameters), so there is nothing to explain. The description could have clarified what kind of comparison is returned (e.g., metrics, charts), but it does not. The baseline for 0 parameters is 4, but the lack of added detail reduces it to 3.

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 clearly states it provides a side-by-side comparison of specific L2 networks (Base, Arbitrum, etc.). The verb 'compare' is implied by 'side-by-side', and the listed resources make the scope distinct from sibling tools which focus on prices, news, or individual entities.

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?

No guidance on when to use this tool versus alternatives. The description does not mention scenarios where this comparison is appropriate or any prerequisites. An agent would have to infer its use case from the name and list.

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