Skip to main content
Glama

manage_models

Create, modify, and organize Anki note types by managing fields, templates, and styling to customize flashcard structure for effective learning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesModel management operation
modelNameNoModel/note type name
fieldsNoField names in order (for create)
templatesNoCard templates (for create)
cssNoCSS styling
isClozeNoIs cloze deletion type
fieldNameNoField name
newFieldNameNoNew field name (for rename)
fieldIndexNoField index position
templateNameNoTemplate name
templateNoTemplate content

Implementation Reference

  • The main handler function for the 'manage_models' tool. It handles various operations (list, create, add_field, remove_field, rename_field, add_template, remove_template, update_styling) on Anki note types (models) using the ankiClient.model API.
    async ({
      operation,
      modelName,
      fields,
      templates,
      css,
      isCloze,
      fieldName,
      newFieldName,
      fieldIndex,
      templateName,
      template,
    }) => {
      try {
        switch (operation) {
          case 'list': {
            const models = await ankiClient.model.modelNamesAndIds();
            const modelList = Object.entries(models)
              .map(([name, id]) => `  • ${name} (ID: ${id})`)
              .join('\n');
            return {
              content: [
                {
                  type: 'text',
                  text: `Note Types (${Object.keys(models).length}):\n${modelList}`,
                },
              ],
            };
          }
    
          case 'create': {
            if (!modelName || !fields || !templates) {
              throw new Error('create requires modelName, fields, and templates');
            }
            const modelParams: any = {
              modelName,
              inOrderFields: fields,
              cardTemplates: templates,
            };
            if (css) modelParams.css = css;
            if (isCloze !== undefined) modelParams.isCloze = isCloze;
    
            const result = await ankiClient.model.createModel(modelParams);
            return {
              content: [
                {
                  type: 'text',
                  text: `✓ Created note type "${modelName}" (ID: ${result.id})`,
                },
              ],
            };
          }
    
          case 'add_field': {
            if (!modelName || !fieldName || fieldIndex === undefined) {
              throw new Error('add_field requires modelName, fieldName, and fieldIndex');
            }
            await ankiClient.model.modelFieldAdd({ modelName, fieldName, index: fieldIndex });
            return {
              content: [
                {
                  type: 'text',
                  text: `✓ Added field "${fieldName}" to "${modelName}" at position ${fieldIndex}`,
                },
              ],
            };
          }
    
          case 'remove_field': {
            if (!modelName || !fieldName) {
              throw new Error('remove_field requires modelName and fieldName');
            }
            await ankiClient.model.modelFieldRemove({ modelName, fieldName });
            return {
              content: [
                {
                  type: 'text',
                  text: `✓ Removed field "${fieldName}" from "${modelName}"`,
                },
              ],
            };
          }
    
          case 'rename_field': {
            if (!modelName || !fieldName || !newFieldName) {
              throw new Error('rename_field requires modelName, fieldName, and newFieldName');
            }
            await ankiClient.model.modelFieldRename({
              modelName,
              oldFieldName: fieldName,
              newFieldName,
            });
            return {
              content: [
                {
                  type: 'text',
                  text: `✓ Renamed field "${fieldName}" to "${newFieldName}" in "${modelName}"`,
                },
              ],
            };
          }
    
          case 'add_template': {
            if (!modelName || !template) {
              throw new Error('add_template requires modelName and template');
            }
            await ankiClient.model.modelTemplateAdd({ modelName, template });
            return {
              content: [
                {
                  type: 'text',
                  text: `✓ Added template to "${modelName}"`,
                },
              ],
            };
          }
    
          case 'remove_template': {
            if (!modelName || !templateName) {
              throw new Error('remove_template requires modelName and templateName');
            }
            await ankiClient.model.modelTemplateRemove({ modelName, templateName });
            return {
              content: [
                {
                  type: 'text',
                  text: `✓ Removed template "${templateName}" from "${modelName}"`,
                },
              ],
            };
          }
    
          case 'update_styling': {
            if (!modelName || !css) {
              throw new Error('update_styling requires modelName and css');
            }
            await ankiClient.model.updateModelStyling({ model: { name: modelName, css } });
            return {
              content: [
                {
                  type: 'text',
                  text: `✓ Updated styling for "${modelName}"`,
                },
              ],
            };
          }
    
          default:
            throw new Error(`Unknown operation: ${operation}`);
        }
      } catch (error) {
        throw new Error(
          `manage_models failed: ${error instanceof Error ? error.message : String(error)}`
        );
      }
    }
  • Zod schema defining the input parameters for the 'manage_models' tool, including the operation enum and conditional fields for different operations.
    {
      operation: z
        .enum([
          'list',
          'create',
          'add_field',
          'remove_field',
          'rename_field',
          'add_template',
          'remove_template',
          'update_styling',
        ])
        .describe('Model management operation'),
    
      modelName: z.string().optional().describe('Model/note type name'),
    
      // For create
      fields: z.array(z.string()).optional().describe('Field names in order (for create)'),
      templates: z
        .array(
          z.object({
            Front: z.string(),
            Back: z.string(),
          })
        )
        .optional()
        .describe('Card templates (for create)'),
      css: z.string().optional().describe('CSS styling'),
      isCloze: z.boolean().optional().describe('Is cloze deletion type'),
    
      // For field operations
      fieldName: z.string().optional().describe('Field name'),
      newFieldName: z.string().optional().describe('New field name (for rename)'),
      fieldIndex: z.number().optional().describe('Field index position'),
    
      // For template operations
      templateName: z.string().optional().describe('Template name'),
      template: z
        .object({
          Front: z.string(),
          Back: z.string(),
        })
        .optional()
        .describe('Template content'),
    },
  • Registration of the 'manage_models' tool using server.tool(), including schema and handler.
    server.tool(
      'manage_models',
      {
        operation: z
          .enum([
            'list',
            'create',
            'add_field',
            'remove_field',
            'rename_field',
            'add_template',
            'remove_template',
            'update_styling',
          ])
          .describe('Model management operation'),
    
        modelName: z.string().optional().describe('Model/note type name'),
    
        // For create
        fields: z.array(z.string()).optional().describe('Field names in order (for create)'),
        templates: z
          .array(
            z.object({
              Front: z.string(),
              Back: z.string(),
            })
          )
          .optional()
          .describe('Card templates (for create)'),
        css: z.string().optional().describe('CSS styling'),
        isCloze: z.boolean().optional().describe('Is cloze deletion type'),
    
        // For field operations
        fieldName: z.string().optional().describe('Field name'),
        newFieldName: z.string().optional().describe('New field name (for rename)'),
        fieldIndex: z.number().optional().describe('Field index position'),
    
        // For template operations
        templateName: z.string().optional().describe('Template name'),
        template: z
          .object({
            Front: z.string(),
            Back: z.string(),
          })
          .optional()
          .describe('Template content'),
      },
      async ({
        operation,
        modelName,
        fields,
        templates,
        css,
        isCloze,
        fieldName,
        newFieldName,
        fieldIndex,
        templateName,
        template,
      }) => {
        try {
          switch (operation) {
            case 'list': {
              const models = await ankiClient.model.modelNamesAndIds();
              const modelList = Object.entries(models)
                .map(([name, id]) => `  • ${name} (ID: ${id})`)
                .join('\n');
              return {
                content: [
                  {
                    type: 'text',
                    text: `Note Types (${Object.keys(models).length}):\n${modelList}`,
                  },
                ],
              };
            }
    
            case 'create': {
              if (!modelName || !fields || !templates) {
                throw new Error('create requires modelName, fields, and templates');
              }
              const modelParams: any = {
                modelName,
                inOrderFields: fields,
                cardTemplates: templates,
              };
              if (css) modelParams.css = css;
              if (isCloze !== undefined) modelParams.isCloze = isCloze;
    
              const result = await ankiClient.model.createModel(modelParams);
              return {
                content: [
                  {
                    type: 'text',
                    text: `✓ Created note type "${modelName}" (ID: ${result.id})`,
                  },
                ],
              };
            }
    
            case 'add_field': {
              if (!modelName || !fieldName || fieldIndex === undefined) {
                throw new Error('add_field requires modelName, fieldName, and fieldIndex');
              }
              await ankiClient.model.modelFieldAdd({ modelName, fieldName, index: fieldIndex });
              return {
                content: [
                  {
                    type: 'text',
                    text: `✓ Added field "${fieldName}" to "${modelName}" at position ${fieldIndex}`,
                  },
                ],
              };
            }
    
            case 'remove_field': {
              if (!modelName || !fieldName) {
                throw new Error('remove_field requires modelName and fieldName');
              }
              await ankiClient.model.modelFieldRemove({ modelName, fieldName });
              return {
                content: [
                  {
                    type: 'text',
                    text: `✓ Removed field "${fieldName}" from "${modelName}"`,
                  },
                ],
              };
            }
    
            case 'rename_field': {
              if (!modelName || !fieldName || !newFieldName) {
                throw new Error('rename_field requires modelName, fieldName, and newFieldName');
              }
              await ankiClient.model.modelFieldRename({
                modelName,
                oldFieldName: fieldName,
                newFieldName,
              });
              return {
                content: [
                  {
                    type: 'text',
                    text: `✓ Renamed field "${fieldName}" to "${newFieldName}" in "${modelName}"`,
                  },
                ],
              };
            }
    
            case 'add_template': {
              if (!modelName || !template) {
                throw new Error('add_template requires modelName and template');
              }
              await ankiClient.model.modelTemplateAdd({ modelName, template });
              return {
                content: [
                  {
                    type: 'text',
                    text: `✓ Added template to "${modelName}"`,
                  },
                ],
              };
            }
    
            case 'remove_template': {
              if (!modelName || !templateName) {
                throw new Error('remove_template requires modelName and templateName');
              }
              await ankiClient.model.modelTemplateRemove({ modelName, templateName });
              return {
                content: [
                  {
                    type: 'text',
                    text: `✓ Removed template "${templateName}" from "${modelName}"`,
                  },
                ],
              };
            }
    
            case 'update_styling': {
              if (!modelName || !css) {
                throw new Error('update_styling requires modelName and css');
              }
              await ankiClient.model.updateModelStyling({ model: { name: modelName, css } });
              return {
                content: [
                  {
                    type: 'text',
                    text: `✓ Updated styling for "${modelName}"`,
                  },
                ],
              };
            }
    
            default:
              throw new Error(`Unknown operation: ${operation}`);
          }
        } catch (error) {
          throw new Error(
            `manage_models failed: ${error instanceof Error ? error.message : String(error)}`
          );
        }
      }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/arielbk/anki-mcp'

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