Skip to main content
Glama
komer3

Linode MCP Server

by komer3

list_regions

Retrieve all available Linode cloud regions to determine where to deploy or manage instances.

Instructions

List all available Linode regions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'list_regions' tool. It uses the LinodeClient to fetch all regions, processes them into a list of dictionaries with id, country, status, and capabilities, and returns the JSON string. Includes error handling. Registered via the @mcp_server.tool() decorator.
    @mcp_server.tool()
    def list_regions() -> str:
        """List all available Linode regions"""
        try:
            # Get the regions list
            regions_list = linode_client.regions()
            
            # Process each region in the collection
            result = []
            # Type annotation to help linter
            for item in regions_list:
                # Cast to Region type to resolve linting issues
                region = cast(Region, item)
                result.append({
                    "id": region.id,
                    "country": region.country,
                    "status": region.status,
                    "capabilities": region.capabilities
                })
                
            return json.dumps(result)
        except Exception as e:
            logger.error(f"Error listing regions: {str(e)}")
            return json.dumps({"error": str(e)})
  • The call to register_tools(mcp, linode_client) which triggers the registration of the list_regions tool (and others) via decorators in linode_tools.py.
    # Register tools from the linode_tools module
    logger.debug("Registering Linode tools with MCP server")
    register_tools(mcp, linode_client)
  • The register_tools function where the @mcp_server.tool() decorators are applied to define and register the list_regions tool.
    def register_tools(mcp_server: Any, linode_client: LinodeClient):
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'List all available Linode regions' but does not specify behavioral traits like whether the list is static or dynamic, if there are rate limits, authentication requirements, or how the data is formatted. This leaves significant gaps in understanding the tool's operation.

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 a single, clear sentence with no wasted words, making it highly efficient and easy to parse. It is front-loaded with the core action and resource, providing all necessary information in a minimal format without redundancy or unnecessary elaboration.

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?

Given the tool's simplicity (0 parameters, no annotations, but with an output schema), the description is minimally adequate. It states the purpose but lacks behavioral context, which is a gap since no annotations cover this. The output schema may handle return values, but the description does not address usage or operational traits, leaving it incomplete for full understanding.

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?

The input schema has 0 parameters with 100% coverage, meaning no parameters need documentation. The description does not add parameter details, which is appropriate here. It implies no filtering or options, aligning with the empty schema, so it compensates adequately for the lack of parameters.

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 the action ('List') and resource ('all available Linode regions'), making the tool's purpose immediately understandable. It lacks sibling tools for differentiation, but the verb+resource combination is specific enough for a standalone tool. No tautology or misleading elements are present.

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 provides no guidance on when to use this tool, such as prerequisites, alternatives, or specific contexts. It simply states what the tool does without indicating scenarios where it might be preferred or avoided. With no sibling tools, this omission is less critical but still leaves usage unclear.

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/komer3/linode-mcp'

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