Skip to main content
Glama

portal_list_networks

Find and filter blockchain networks by VM family, network type, name, or alias to identify the correct chain for your queries.

Instructions

Find the right network or chain name to use across EVM, Solana, Bitcoin, Substrate, and Hyperliquid.

COMMON USER ASKS:

  • Find Base-like networks

  • Show Solana mainnets

  • Show Substrate mainnets

FIRST CHOICE FOR:

  • finding the correct network before any other query

WHEN TO USE:

  • You are not sure which network name, chain name, or alias to use.

  • You want to filter networks by VM family, network type, or real-time availability.

DON'T USE:

  • You already know the exact network and want live data from that network.

EXAMPLES:

  • Find Base-like networks: {"query":"base","limit":10}

  • Show Solana mainnets: {"vm":"solana","network_type":"mainnet"}

  • Show Substrate mainnets: {"vm":"substrate","network_type":"mainnet"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vmNoFilter by VM family
limitNoMax results to return (default: 25, max: 100)
queryNoSearch by name, alias, or chain ID
network_typeNoFilter by network type
real_time_onlyNoOnly show networks with a real-time indexed head
Behavior4/5

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

With no annotations, the description carries full burden for transparency. It discloses that the tool returns networks filtered by parameters like vm, network_type, real_time_only, query, and limit. It mentions 'real-time indexed head' filter but does not elaborate on what that means. Overall, it adequately describes the read-only, listing behavior.

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?

The description is well-structured with sections (COMMON USER ASKS, FIRST CHOICE FOR, WHEN TO USE, DON'T USE, EXAMPLES). It is front-loaded with the main purpose. Though slightly verbose (multiple sections), each part serves a clear role and adds information without redundancy.

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 tool's complexity (5 parameters, no output schema, many siblings), the description provides sufficient context. It explains when to use this tool over siblings, covers common use cases, and gives examples. It does not detail the return format, but for a list tool, the examples implicitly show the kind of results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with each parameter documented. The description adds value beyond the schema by providing concrete examples of parameter usage (e.g., query: 'base', vm: 'solana', network_type: 'mainnet'). This helps agents understand how to combine parameters effectively.

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 tool's purpose: to find the right network or chain name across multiple blockchain families. It uses specific verbs ('Find', 'Show') and explicitly lists supported VMs, distinguishing it from sibling tools that perform analytics or queries on specific networks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidelines: when to use (unsure of network names, filter by VM/type/availability) and when not to use (already know exact network). It also gives common user asks and example queries, making the usage context crystal clear.

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/subsquid-labs/portal-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server