Skip to main content
Glama

create_account

Create an account with name, email, phone, address, labels, and signup answers.

Instructions

Create an account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesArbitrary string representing the name of the account. Is autogenerated for personal accounts.
emailNoA string representing the billing e-mail of the account
phoneNoA string representing the phone number of the account
label_idsNoIDs of the labels
customNoThe custom properties of the account.
address_attributesNo
signup_answers_attributesNo

Implementation Reference

  • Handler function for the create_account tool. Calls apiPost('/accounts', body) to create an account via the Eduframe API, logs the response, and returns a formatted success message.
    async (body) => {
      try {
        const record = await apiPost<EduframeRecord>("/accounts", body);
        void logResponse("create_account", body, record);
        return formatCreate(record, "account");
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for create_account tool defined using Zod, including fields: name (required), email, phone, label_ids, custom, address_attributes (with nested fields), and signup_answers_attributes.
    {
      description: "Create an account",
      annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: false },
      inputSchema: {
        name: z
          .string()
          .describe("Arbitrary string representing the name of the account. Is autogenerated for personal accounts."),
        email: z.string().optional().describe("A string representing the billing e-mail of the account"),
        phone: z.string().optional().describe("A string representing the phone number of the account"),
        label_ids: z.array(z.number().int()).optional().describe("IDs of the labels"),
        custom: z.object({}).optional().describe("The custom properties of the account."),
        address_attributes: z
          .object({
            addressee: z.string().optional().describe("The addressee of the address."),
            address: z.string().describe("Concatenation of the street and house number."),
            address_line2: z.string().optional().describe("A string representing the second line of the address."),
            postal_code: z.string().describe("A string representing the postal code."),
            city: z.string().describe("A string representing the city."),
            state_province: z.string().optional().describe("An letter USA state code."),
            country: z.string().describe("An ISO3166 two-letter country code."),
          })
          .optional(),
        signup_answers_attributes: z
          .array(
            z.object({
              signup_question_id: z.number().int().describe("Unique identifier of the question."),
              value: z
                .union([z.string(), z.boolean(), z.array(z.string())])
                .describe("The formatted value of the answer."),
            }),
          )
          .optional(),
      },
  • Registration of the create_account tool via server.registerTool() within the registerAccountTools function.
    server.registerTool(
      "create_account",
      {
        description: "Create an account",
        annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: false },
        inputSchema: {
          name: z
            .string()
            .describe("Arbitrary string representing the name of the account. Is autogenerated for personal accounts."),
          email: z.string().optional().describe("A string representing the billing e-mail of the account"),
          phone: z.string().optional().describe("A string representing the phone number of the account"),
          label_ids: z.array(z.number().int()).optional().describe("IDs of the labels"),
          custom: z.object({}).optional().describe("The custom properties of the account."),
          address_attributes: z
            .object({
              addressee: z.string().optional().describe("The addressee of the address."),
              address: z.string().describe("Concatenation of the street and house number."),
              address_line2: z.string().optional().describe("A string representing the second line of the address."),
              postal_code: z.string().describe("A string representing the postal code."),
              city: z.string().describe("A string representing the city."),
              state_province: z.string().optional().describe("An letter USA state code."),
              country: z.string().describe("An ISO3166 two-letter country code."),
            })
            .optional(),
          signup_answers_attributes: z
            .array(
              z.object({
                signup_question_id: z.number().int().describe("Unique identifier of the question."),
                value: z
                  .union([z.string(), z.boolean(), z.array(z.string())])
                  .describe("The formatted value of the answer."),
              }),
            )
            .optional(),
        },
      },
      async (body) => {
        try {
          const record = await apiPost<EduframeRecord>("/accounts", body);
          void logResponse("create_account", body, record);
          return formatCreate(record, "account");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • registerAccountTools is included in the tools array and called by registerAllTools to register all tools on the MCP server.
    const tools: Array<(server: McpServer) => void> = [
      registerAccountTools,
  • apiPost helper function used by the create_account handler to POST JSON data to the Eduframe API.
    export async function apiPost<T>(path: string, body: unknown): Promise<T> {
      const { token } = getConfig();
      const url = buildUrl(path);
    
      const response = await fetch(url.toString(), {
        method: "POST",
        headers: buildHeaders(token),
        body: JSON.stringify(body),
      });
    
      return handleResponse<T>(response);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are all false (readOnlyHint, destructiveHint, idempotentHint), and the description doesn't add any behavioral context such as side effects, authorization requirements, or response behavior. The description should compensate for the lack of annotation detail but fails to do so.

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

Conciseness2/5

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

The description is only three words, which is too terse and fails to convey meaningful context. It is not concise in a helpful way; it under-specifies the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, nested objects, no output schema, no annotations), the description is completely inadequate. It lacks details about required fields, return values, and behavioral implications.

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 71%, which is relatively high, so the schema already documents most parameters. The description adds no additional meaning beyond the schema, so a score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create an account' is a tautology, restating the tool name without specifying what type of account (e.g., user, organization) or distinguishing it from sibling tools like create_user or create_lead.

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. No prerequisites, context, or exclusion criteria are mentioned.

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/martijnpieters/eduframe-mcp'

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