Skip to main content
Glama

get_managed_transform

Query managed transform configuration for Edge Security Acceleration sites to retrieve security settings and deployment parameters.

Instructions

Query Managed Transform Configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID, which can be obtained by calling ListSites.
siteVersionNoThe version number of the site. For sites with version management enabled, you can use this parameter to specify the effective version of the configuration, defaulting to version 0.

Implementation Reference

  • The core handler function implementing the 'get_managed_transform' tool logic. It processes the MCP CallToolRequest, invokes the API service, and formats the response.
    export const get_managed_transform = async (request: CallToolRequest) => {
      const res = await api.getManagedTransform(
        request.params.arguments as GetManagedTransformRequest,
      );
    
      return {
        content: [{ type: 'text', text: JSON.stringify(res) }],
        success: true,
      };
    };
  • The Tool object defining the schema, name, description, and annotations for the 'get_managed_transform' tool, including input validation schema.
    export const GET_MANAGED_TRANSFORM_TOOL: Tool = {
      name: 'get_managed_transform',
      description: 'Query Managed Transform Configuration.',
      inputSchema: {
        type: 'object',
        properties: {
          siteId: {
            type: 'number',
            description: 'Site ID, which can be obtained by calling ListSites.',
            example: [12228828888],
          },
          siteVersion: {
            type: 'number',
            description:
              'The version number of the site. For sites with version management enabled, you can use this parameter to specify the effective version of the configuration, defaulting to version 0.',
            example: [0],
          },
        },
        required: ['siteId'],
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: false,
        },
      },
    };
  • Registration of the tool handler in the esaHandlers object, mapping 'get_managed_transform' to its function (line 200). This is likely used by the MCP server to dispatch calls.
    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,
    };
  • Includes the GET_MANAGED_TRANSFORM_TOOL in the managed transform tools list, which is merged into the main ESA_OPENAPI_LIST for tool discovery.
    export const MANAGED_TRANSFORM_LIST = [
      UPDATE_MANAGED_TRANSFORM_TOOL,
      GET_MANAGED_TRANSFORM_TOOL,
    ];
  • Helper method in the API service client that wraps the Alibaba Cloud ESA client call for getManagedTransform, used by the tool handler.
    getManagedTransform(params: GetManagedTransformRequest) {
      const request = new GetManagedTransformRequest(params);
      return this.callApi(
        this.client.getManagedTransform.bind(this.client) as ApiMethod<
          GetManagedTransformRequest,
          GetManagedTransformResponse
        >,
        request,
      );
    }
Behavior3/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. 'Query' implies a read-only operation, which is accurate, but it doesn't disclose behavioral traits like authentication needs, rate limits, error conditions, or what the query returns. The description is minimal and lacks operational context.

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 a simple query 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 the complexity (a read operation with required parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'Managed Transform Configuration' entails, what data is returned, or any prerequisites, leaving significant gaps for the agent to understand the tool's full context.

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 schema fully documents both parameters (siteId and siteVersion). The description adds no additional meaning beyond what's in the schema, such as explaining the relationship between these parameters or typical use cases. Baseline 3 is appropriate when the schema does the heavy lifting.

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 resource ('Managed Transform Configuration'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'update_managed_transform' or explain what 'Managed Transform Configuration' specifically refers to in this context.

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 sibling tools like 'update_managed_transform' for modifications or 'list_sites' to obtain the required siteId, leaving the agent without context for 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/aliyun/mcp-server-esa'

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