Skip to main content
Glama

close_model

Close an Anaplan model to archive it. Requires workspace admin and must be done before bulk deletion of models.

Instructions

Close (archive) a model. Requires workspace admin. Must be closed before bulk_delete_models.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesAnaplan workspace ID or name
modelIdYesAnaplan model ID or name

Implementation Reference

  • The async handler function that executes the close_model tool logic: resolves workspace/model IDs, calls modelManagement.close(), and returns a success message.
    }, async ({ workspaceId, modelId }) => {
      const wId = await resolver.resolveWorkspace(workspaceId);
      const mId = await resolver.resolveModel(wId, modelId);
      await apis.modelManagement.close(wId, mId);
      return { content: [{ type: "text" as const, text: `Model ${mId} closed successfully.` }] };
    });
  • The tool registration with Zod schema defining two string parameters (workspaceId, modelId) and a description.
    server.tool("close_model", "Close (archive) a model. Requires workspace admin. Must be closed before bulk_delete_models.", {
      workspaceId: z.string().describe("Anaplan workspace ID or name"),
      modelId: z.string().describe("Anaplan model ID or name"),
  • Registration of 'close_model' tool on the MCP server via server.tool() call, within registerBulkTools() function.
    server.tool("close_model", "Close (archive) a model. Requires workspace admin. Must be closed before bulk_delete_models.", {
      workspaceId: z.string().describe("Anaplan workspace ID or name"),
      modelId: z.string().describe("Anaplan model ID or name"),
    }, async ({ workspaceId, modelId }) => {
      const wId = await resolver.resolveWorkspace(workspaceId);
      const mId = await resolver.resolveModel(wId, modelId);
      await apis.modelManagement.close(wId, mId);
      return { content: [{ type: "text" as const, text: `Model ${mId} closed successfully.` }] };
    });
  • The close() method in ModelManagementApi class that makes the HTTP POST request to /workspaces/{wId}/models/{mId}/close endpoint.
    async close(workspaceId: string, modelId: string) {
      return this.client.post<any>(`/workspaces/${workspaceId}/models/${modelId}/close`);
    }
Behavior2/5

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

With no annotations, description must disclose behavioral traits. It only mentions admin requirement and prerequisite, but lacks details on side effects, reversibility, or error conditions.

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?

Two sentences, front-loaded with action and requirements, no fluff.

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

Completeness3/5

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

Provides essential context for a simple archive action, but lacks details like idempotency or what happens if model already closed. Adequate given no output schema.

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 coverage is 100%, so description adds no value beyond schema. Baseline of 3 is appropriate as it does not detract.

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

Purpose5/5

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

The description clearly states the action (close/archive a model) and distinguishes it from siblings like 'open_model' and 'bulk_delete_models' by mentioning the prerequisite.

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

Usage Guidelines4/5

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

Provides clear context: requires workspace admin and must be done before bulk_delete_models. No explicit when-not or alternative guidance, but enough for common use.

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/larasrinath/anaplan-mcp'

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