Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_bill_info

Retrieve billing details for a specified month from Sakura Cloud infrastructure management.

Instructions

Get billing information for a specific month

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesThe year (YYYY) of the billing period
monthYesThe month (MM) of the billing period

Implementation Reference

  • Handler function that executes the get_bill_info tool: validates input, calls fetchFromSakuraCloud with /bill/YYYYMM path, and returns JSON response.
    } else if (request.params.name === 'get_bill_info') {
      try {
        validateCredentials();
        
        const year = request.params.arguments?.year as string;
        const month = request.params.arguments?.month as string;
        
        if (!year || !month) {
          throw new Error('Year and month are required for billing information');
        }
        
        const billInfo = await fetchFromSakuraCloud(`/bill/${year}${month}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(billInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Tool registration in ListToolsRequestSchema handler, defining name, description, and input schema.
      name: 'get_bill_info',
      description: 'Get billing information for a specific month',
      inputSchema: {
        type: 'object',
        properties: {
          year: {
            type: 'string',
            description: 'The year (YYYY) of the billing period'
          },
          month: {
            type: 'string',
            description: 'The month (MM) of the billing period'
          }
        },
        required: ['year', 'month']
      }
    },
  • Input schema definition for get_bill_info tool, specifying year and month as required string parameters.
      type: 'object',
      properties: {
        year: {
          type: 'string',
          description: 'The year (YYYY) of the billing period'
        },
        month: {
          type: 'string',
          description: 'The month (MM) of the billing period'
        }
      },
      required: ['year', 'month']
    }
  • Primary helper function for making HTTPS API requests to Sakura Cloud, used by get_bill_info handler.
    async function fetchFromSakuraCloud(path: string, isPublicAPI: boolean = false, zone: string = DEFAULT_ZONE, method: string = 'GET', bodyData?: any): Promise<any> {
      return new Promise((resolve, reject) => {
        const basePath = isPublicAPI ? '/cloud/api/cloud/1.1' : `/cloud/zone/${zone}/api/cloud/1.1`;
        
        const options = {
          hostname: 'secure.sakura.ad.jp',
          port: 443,
          path: `${basePath}${path}`,
          method: method,
          headers: {
            'Accept': 'application/json',
            'Authorization': '',
            'Content-Type': 'application/json'
          }
        };
        
        // Add authorization for non-public APIs
        if (!isPublicAPI) {
          options.headers['Authorization'] = `Basic ${Buffer.from(`${SACLOUD_API_TOKEN}:${SACLOUD_API_SECRET}`).toString('base64')}`;
        }
    
        const req = https.request(options, (res) => {
          let data = '';
          
          res.on('data', (chunk) => {
            data += chunk;
          });
          
          res.on('end', () => {
            try {
              if (data) {
                const parsedData = JSON.parse(data);
                resolve(parsedData);
              } else {
                resolve({});
              }
            } catch (err) {
              reject(new Error(`Failed to parse response: ${err}`));
            }
          });
        });
        
        req.on('error', (error) => {
          reject(error);
        });
        
        if (bodyData && (method === 'POST' || method === 'PUT')) {
          req.write(JSON.stringify(bodyData));
        }
        
        req.end();
      });
    }
  • Helper function to validate presence of Sakura Cloud API credentials, called in get_bill_info handler.
    function validateCredentials(): void {
      if (!SACLOUD_API_TOKEN || !SACLOUD_API_SECRET) {
        throw new Error('Missing API credentials. Set SACLOUD_API_TOKEN and SACLOUD_API_SECRET environment variables.');
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether this is a read-only operation (implied by 'Get' but not explicit), authentication requirements, rate limits, error conditions, or what format the billing information returns. For a tool with zero annotation coverage, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without being overly terse.

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 the tool has no annotations and no output schema, the description is incomplete. It doesn't explain what 'billing information' includes (e.g., summary vs. details), potential return formats, or any behavioral context needed for safe invocation. For a tool with 2 parameters and no structured output documentation, this leaves significant gaps.

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 description mentions 'for a specific month' which implies parameters for time period, aligning with the schema's year and month parameters. Since schema description coverage is 100% (both parameters are well-documented in the schema), the description adds minimal value beyond what's already in structured data, meeting the baseline score.

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 verb ('Get') and resource ('billing information') with specific scope ('for a specific month'), making the purpose unambiguous. However, it doesn't differentiate from sibling 'get_bill_detail' which might provide more granular billing data, so it doesn't reach the highest score.

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 versus alternatives like 'get_bill_detail' or other billing-related tools. It doesn't mention prerequisites, constraints, or typical use cases, leaving the agent with minimal contextual direction.

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/hidenorigoto/sacloud-mcp'

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