Skip to main content
Glama

get_certificate

Retrieve SSL/TLS certificates, private keys, and certificate details for websites managed through Edge Security Acceleration services.

Instructions

Retrieve the certificate, private key, and certificate information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesThe website ID. Reference Value Source: list_sites
idYesCertificate ID. Example: babaded901474b9693acf530e0fb1d95

Implementation Reference

  • Tool schema definition for 'get_certificate', including input schema with siteId and id parameters.
    export const GET_CERTIFICATE_TOOL: Tool = {
      name: 'get_certificate',
      description:
        'Retrieve the certificate, private key, and certificate information',
      inputSchema: {
        type: 'object',
        properties: {
          siteId: {
            type: 'number',
            description: 'The website ID. Reference Value Source: list_sites',
          },
          id: {
            type: 'string',
            description:
              'Certificate ID. Example: babaded901474b9693acf530e0fb1d95',
          },
        },
        required: ['siteId', 'id'],
        annotations: {},
      },
    };
  • The main handler function for the get_certificate tool. It extracts arguments, calls api.getCertificate, and returns the JSON-stringified response.
    export const get_certificate = async (request: CallToolRequest) => {
      const res = await api.getCertificate(
        request.params.arguments as GetCertificateRequest,
      );
    
      return {
        content: [{ type: 'text', text: JSON.stringify(res) }],
        success: true,
      };
  • Registration of the get_certificate handler in the esaHandlers object, which maps tool names to their handler functions.
    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 performs the actual getCertificate API call to Alibaba Cloud ESA.
    getCertificate(params: GetCertificateRequest) {
      const request = new GetCertificateRequest(params);
      return this.callApi(
        this.client.getCertificate.bind(this.client) as ApiMethod<
          GetCertificateRequest,
          GetCertificateResponse
        >,
        request,
      );
    }
  • Registration of the GET_CERTIFICATE_TOOL in the CERTIFICATE_LIST array, likely used for tool listing or OpenAPI.
    export const CERTIFICATE_LIST = [
      SET_CERTIFICATE_TOOL,
      APPLY_CERTIFICATE_TOOL,
      GET_CERTIFICATE_TOOL,
      DELETE_CERTIFICATE_TOOL,
      LIST_CERTIFICATES_TOOL,
      GET_CERTIFICATE_QUOTA_TOOL,
    ];
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 the action 'retrieve' but lacks critical behavioral details: whether this requires authentication, rate limits, if it's idempotent, what happens if the certificate doesn't exist, or the format of returned information. For a tool handling sensitive data like private keys, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the core action and resources. There's no wasted wording, though it could be slightly more structured (e.g., separating key components). It earns its place by clearly stating what the tool does.

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 for a tool that retrieves sensitive data (certificate and private key). It doesn't cover authentication needs, error conditions, return format, or security implications. For a 2-parameter tool with zero annotation coverage, this leaves significant gaps for an AI agent.

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%, with both parameters ('siteId' and 'id') well-documented in the schema. The description adds no additional parameter context beyond implying retrieval of certificate-related data. Since the schema handles parameter documentation adequately, the 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 'retrieve' and specifies the resources: 'certificate, private key, and certificate information'. It distinguishes from sibling tools like 'list_certificates' (which lists certificates) and 'delete_certificate' (which removes them). However, it doesn't explicitly differentiate from 'set_certificate' or 'apply_certificate', which might involve similar resources.

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 (e.g., needing a certificate ID from 'list_certificates'), exclusions, or comparisons to siblings like 'get_certificate_quota' or 'list_certificates'. Usage is implied only by the action 'retrieve'.

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