Skip to main content
Glama

er_record_create

Create a new record for an Edge Routine to manage configurations and settings for edge security acceleration services.

Instructions

Create a new record associated with an Edge Routine (ER)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the routine
siteIdYesThe ID of the site
recordNameYesThe name of the record

Implementation Reference

  • The main handler function that implements the logic for the 'er_record_create' tool by calling the API to create a routine-related record.
    export const er_record_create = async (request: CallToolRequest) => {
      const res = await api.createRoutineRelatedRecord(
        request.params.arguments as CreateRoutineRelatedRecordRequest,
      );
    
      return {
        content: [{ type: 'text', text: JSON.stringify(res) }],
        success: true,
      };
    };
  • The Tool object definition for 'er_record_create', which includes the input schema for validation.
    export const ER_RECORD_CREATE_TOOL: Tool = {
      name: 'er_record_create',
      description: 'Create a new record associated with an Edge Routine (ER)',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'The name of the routine',
          },
          siteId: {
            type: 'number',
            description: 'The ID of the site',
          },
          recordName: {
            type: 'string',
            description: 'The name of the record',
          },
        },
        required: ['name', 'siteId', 'recordName'],
      },
    };
  • Registration of the ER_RECORD_CREATE_TOOL in the ESA_OPENAPI_ER_LIST array, which aggregates ER-related tools.
    export const ESA_OPENAPI_ER_LIST = [
      HTML_DEPLOY_TOOL,
      ROUTINE_CREATE_TOOL,
      ROUTINE_DELETE_TOOL,
      ROUTINE_LIST_TOOL,
      ROUTINE_GET_TOOL,
      ROUTINE_CODE_COMMIT_TOOL,
      ROUTINE_CODE_DEPLOY_TOOL,
      ROUTINE_ROUTE_LIST_TOOL,
      DEPLOYMENT_DELETE_TOOL,
      SITE_ACTIVE_LIST_TOOL,
      SITE_ROUTE_LIST_TOOL,
      ROUTE_CREATE_TOOL,
      ROUTE_DELETE_TOOL,
      ROUTE_UPDATE_TOOL,
      ROUTE_GET_TOOL,
      SITE_MATCH_TOOL,
      ER_RECORD_CREATE_TOOL,
      ER_RECORD_DELETE_TOOL,
      ER_RECORD_LIST_TOOL,
    ];
  • The esaHandlers object registers the er_record_create handler function, mapping tool names to their implementations.
    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,
    };
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 of behavioral disclosure. It states 'Create' implies a write operation, but it doesn't cover permissions, side effects, error handling, or response format. This is a significant gap for a mutation tool with zero annotation coverage.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized, 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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, return values, and usage context, which are critical for an agent to invoke it correctly. The high schema coverage doesn't compensate for these 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?

Schema description coverage is 100%, so the schema already documents all three parameters. The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or usage examples. Baseline 3 is appropriate when the schema handles parameter documentation.

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 action ('Create') and resource ('new record associated with an Edge Routine'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'create_site' or 'routine_create', which also create resources but different types, so it misses full sibling differentiation.

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. For example, it doesn't mention when to choose 'er_record_create' over 'create_site' or 'routine_create', nor does it specify prerequisites or exclusions, leaving usage context 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/aliyun/mcp-server-esa'

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