Skip to main content
Glama
rainhan99

Cloud Manage MCP Server

by rainhan99

get_vultr_instance_bandwidth

Retrieve bandwidth usage data for a Vultr cloud instance to monitor network consumption and track resource utilization.

Instructions

获取Vultr实例带宽使用情况

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:547-552 (handler)
    MCP tool handler function that registers and executes the tool by delegating to the Vultr provider.
    @mcp.tool()
    def get_vultr_instance_bandwidth(instance_id: str) -> Dict:
        """
        获取Vultr实例带宽使用情况
        """
        return vultr_provider.get_instance_bandwidth(instance_id)
  • Core helper method in VultrProvider class that performs the actual API request to Vultr for instance bandwidth data.
    def get_instance_bandwidth(self, instance_id: str) -> Dict:
        """
        获取实例的带宽使用情况
        
        Args:
            instance_id (str): Vultr实例ID
            
        Returns:
            Dict: 带宽信息或错误信息
        """
        if not self.available:
            return {
                'error': f'Vultr服务不可用: {getattr(self, "error", "未知错误")}',
                'provider': 'vultr'
            }
        
        try:
            response = requests.get(f'{self.base_url}/instances/{instance_id}/bandwidth', headers=self.headers, timeout=10)
            
            if response.status_code != 200:
                return {
                    'error': f'获取带宽信息失败: {response.status_code} - {response.text}',
                    'provider': 'vultr'
                }
            
            data = response.json()
            
            return {
                'provider': 'vultr',
                'instance_id': instance_id,
                'bandwidth_data': data.get('bandwidth', {})
            }
            
        except Exception as e:
            return {
                'error': f'获取带宽信息时发生错误: {str(e)}',
                'provider': 'vultr'
            }
Behavior1/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 only states what the tool does without mentioning any behavioral traits such as read-only vs. destructive nature, authentication requirements, rate limits, error handling, or response format. This leaves critical operational details unspecified.

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, efficient sentence in Chinese that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 has an output schema (which handles return values) and a simple input schema with one parameter, the description is minimally adequate. However, with no annotations and low parameter semantics, it lacks completeness for operational context like error cases or usage prerequisites, leaving gaps in understanding the tool's full behavior.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'Vultr实例' (Vultr instance) which implies the 'instance_id' parameter, but adds no meaning beyond the schema's basic type and title. No details on format, constraints, or examples are provided, failing to adequately clarify the single required parameter.

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

Purpose3/5

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

The description '获取Vultr实例带宽使用情况' (Get Vultr instance bandwidth usage) clearly states the verb (get) and resource (Vultr instance bandwidth usage), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_vultr_instance_info' or monitoring tools, leaving ambiguity about what specific bandwidth data is retrieved versus other instance information.

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 is provided on when to use this tool versus alternatives. With siblings like 'get_vultr_instance_info' and monitoring tools for other providers, the description lacks context on whether this is for real-time monitoring, historical data, or specific bandwidth metrics, offering no help in tool selection.

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/rainhan99/cloud_manage_mcp_server'

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