Skip to main content
Glama

get_certificate_quota

Check SSL/TLS certificate quota and usage for a website to monitor available allocations and current consumption.

Instructions

Query certificate quota and usage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesThe website ID. Reference Value Source: list_sites. Example: 1234567890123
typeYesThe type of certificate quota. Example: free

Implementation Reference

  • The handler function implementing the core logic of the 'get_certificate_quota' tool. It receives a CallToolRequest, invokes the API service's getCertificateQuota method with the provided arguments, and returns the response serialized as JSON.
    export const get_certificate_quota = async (request: CallToolRequest) => {
      const res = await api.getCertificateQuota(
        request.params.arguments as GetCertificateQuotaRequest,
      );
    
      return {
        content: [{ type: 'text', text: JSON.stringify(res) }],
        success: true,
      };
    };
  • Tool registration definition for 'get_certificate_quota', including name, description, and input schema specifying required parameters siteId and type.
    export const GET_CERTIFICATE_QUOTA_TOOL: Tool = {
      name: 'get_certificate_quota',
      description: 'Query certificate quota and usage.',
      inputSchema: {
        type: 'object',
        properties: {
          siteId: {
            type: 'number',
            description:
              'The website ID. Reference Value Source: list_sites. Example: 1234567890123',
          },
          type: {
            type: 'string',
            description: 'The type of certificate quota. Example: free',
          },
        },
        required: ['siteId', 'type'],
        annotations: {},
      },
    };
  • Central registration where GET_CERTIFICATE_QUOTA_TOOL is included in the CERTIFICATE_LIST array, which is subsequently merged into the main ESA_OPENAPI_LIST.
    export const CERTIFICATE_LIST = [
      SET_CERTIFICATE_TOOL,
      APPLY_CERTIFICATE_TOOL,
      GET_CERTIFICATE_TOOL,
      DELETE_CERTIFICATE_TOOL,
      LIST_CERTIFICATES_TOOL,
      GET_CERTIFICATE_QUOTA_TOOL,
    ];
  • Global handlers registry (esaHandlers) mapping the 'get_certificate_quota' handler function for tool invocation.
    export const esaHandlers: ToolHandlers = {
      site_active_list,
      site_match,
      site_route_list,
      site_record_list,
      routine_create,
      routine_code_commit,
      routine_delete,
      routine_list,
      routine_get,
      routine_code_deploy,
      routine_route_list,
      deployment_delete,
      route_create,
      route_delete,
      route_update,
      route_get,
      er_record_create,
      er_record_delete,
      er_record_list,
      html_deploy,
      create_site,
      update_site_pause,
      get_site_pause,
      create_site_mx_record,
      create_site_ns_record,
      create_site_txt_record,
      create_site_cname_record,
      create_site_a_or_aaaa_record,
      update_record,
      list_records,
      get_record,
      delete_record,
      update_ipv6,
      get_ipv6,
      update_managed_transform,
      get_managed_transform,
      set_certificate,
      apply_certificate,
      get_certificate,
      delete_certificate,
      list_certificates,
      get_certificate_quota,
      list_sites,
    };
  • Helper method in the API service client that wraps the Alibaba Cloud ESA client's getCertificateQuota call, handling request construction and runtime options.
    getCertificateQuota(params: GetCertificateQuotaRequest) {
      const request = new GetCertificateQuotaRequest(params);
      return this.callApi(
        this.client.getCertificateQuota.bind(this.client) as ApiMethod<
          GetCertificateQuotaRequest,
          GetCertificateQuotaResponse
        >,
        request,
      );
    }
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. It states 'query', implying a read-only operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, error conditions, or what the response includes (e.g., quota details vs. usage statistics). This leaves significant gaps for an agent to understand how to interact with the tool effectively.

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 waste. It's front-loaded and appropriately sized for the tool's complexity, making it easy to parse without unnecessary elaboration.

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 the query returns (e.g., quota limits, current usage), behavioral aspects, or usage context relative to siblings. For a tool with two required parameters and no structured output information, more detail is needed to guide an agent effectively.

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 input schema has 100% description coverage, with clear documentation for both parameters ('siteId' and 'type'). The description adds no additional meaning beyond the schema, such as explaining parameter interactions or providing examples. Since the schema does the heavy lifting, a baseline score of 3 is appropriate.

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 'query' and the resource 'certificate quota and usage', making the purpose understandable. However, it doesn't differentiate from siblings like 'get_certificate' or 'list_certificates', which might also retrieve certificate-related information, so it lacks specific 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. With siblings like 'get_certificate' and 'list_certificates', there's no indication of context, prerequisites, or exclusions for selecting this tool over others.

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/aliyun/mcp-server-esa'

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