Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_coupon_info

Retrieve details for a specific coupon by providing its ID to access discount information and terms.

Instructions

Get information about a specific coupon

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
couponIdYesThe ID of the coupon to retrieve

Implementation Reference

  • Handler implementation for the 'get_coupon_info' tool. Validates credentials, retrieves the coupon ID from arguments, fetches coupon details from Sakura Cloud API endpoint `/coupon/{couponId}`, and returns the JSON response.
    } else if (request.params.name === 'get_coupon_info') {
      try {
        validateCredentials();
        
        const couponId = request.params.arguments?.couponId as string;
        if (!couponId) {
          throw new Error('Coupon ID is required');
        }
        
        const couponInfo = await fetchFromSakuraCloud(`/coupon/${couponId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(couponInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Tool registration in ListToolsRequestSchema handler, including name, description, and input schema definition.
    {
      name: 'get_coupon_info',
      description: 'Get information about a specific coupon',
      inputSchema: {
        type: 'object',
        properties: {
          couponId: {
            type: 'string',
            description: 'The ID of the coupon to retrieve'
          }
        },
        required: ['couponId']
      }
    },
  • Input schema for 'get_coupon_info' tool: requires 'couponId' string.
    {
      name: 'get_coupon_info',
      description: 'Get information about a specific coupon',
      inputSchema: {
        type: 'object',
        properties: {
          couponId: {
            type: 'string',
            description: 'The ID of the coupon to retrieve'
          }
        },
        required: ['couponId']
      }
    },
  • Shared helper function `fetchFromSakuraCloud` used by the tool handler to make authenticated HTTPS requests to Sakura Cloud API.
    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();
      });
    }
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 it retrieves information without disclosing behavioral traits like read-only nature, error handling, authentication needs, or rate limits. It's minimal and lacks essential context for safe use.

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 no wasted words, front-loading the core action. It's appropriately sized for a simple retrieval tool, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what information is returned, error conditions, or behavioral aspects, making it inadequate for a tool that likely involves data retrieval with potential constraints.

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?

Schema description coverage is 100%, so the input schema fully documents the single parameter 'couponId'. The description adds no additional meaning beyond implying retrieval of a specific coupon, aligning with the baseline for high schema coverage.

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 the resource 'information about a specific coupon', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_product_info' or 'get_license_info' beyond the resource type, missing explicit sibling distinction.

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. It doesn't mention prerequisites, context for coupon retrieval, or compare to other 'get_*' tools in the sibling list, leaving 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/hidenorigoto/sacloud-mcp'

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