Skip to main content
Glama

show_imports

List all import actions configured in an Anaplan model to review and prepare for execution.

Instructions

List available import actions in a model. Use show_importdetails to see source file and mapping, then run_import to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesAnaplan workspace ID or name
modelIdYesAnaplan model ID or name
limitNoMax items to return (default 50, max 1000)
searchNoFilter by name or ID (case-insensitive substring match)

Implementation Reference

  • The handler function for the 'show_imports' tool. Accepts workspaceId, modelId, and optional pagination params (limit, search). Resolves workspace and model IDs, calls apis.imports.list(), and returns a formatted table with Name, Type, and ID columns.
    server.tool("show_imports", "List available import actions in a model. Use show_importdetails to see source file and mapping, then run_import to execute.", {
      workspaceId: z.string().describe("Anaplan workspace ID or name"),
      modelId: z.string().describe("Anaplan model ID or name"),
      ...paginationParams,
    }, async ({ workspaceId, modelId, limit, search }) => {
      const wId = await resolver.resolveWorkspace(workspaceId);
      const mId = await resolver.resolveModel(wId, modelId);
      const imports = await apis.imports.list(wId, mId);
      return tableResult(imports, [{ header: "Name", key: "name" }, { header: "Type", key: "importType" }, { header: "ID", key: "id" }], "imports", { limit, search });
    });
  • Input schema for show_imports: workspaceId (string), modelId (string), plus pagination params (limit number, search string).
    server.tool("show_imports", "List available import actions in a model. Use show_importdetails to see source file and mapping, then run_import to execute.", {
      workspaceId: z.string().describe("Anaplan workspace ID or name"),
      modelId: z.string().describe("Anaplan model ID or name"),
      ...paginationParams,
  • The show_imports tool is registered via server.tool() call inside registerExplorationTools() at line 263 of src/tools/exploration.ts.
    export function registerExplorationTools(server: McpServer, apis: ExplorationApis, resolver: NameResolver) {
  • The ImportsApi.list() helper method called by the show_imports handler. Makes a GET request to /workspaces/{workspaceId}/models/{modelId}/imports.
    async list(workspaceId: string, modelId: string) {
      return this.client.getAll<any>(
        `/workspaces/${workspaceId}/models/${modelId}/imports`, "imports"
      );
    }
  • The formatTable() helper function used to format the results into a table with filtering by search and limiting by count.
    export function formatTable(items: any[], columns: Column[], label: string, options?: FormatOptions): FormatResult {
      if (items.length === 0) return { table: "", footer: `No ${label} found.` };
    
      const search = options?.search?.toLowerCase();
      const limit = Math.min(Math.max(1, options?.limit ?? DEFAULT_LIMIT), MAX_LIMIT);
      const searchableKeys = Array.from(new Set(["name", "id", ...columns.map((c) => c.key)]));
    
      // Filter by search (case-insensitive substring on key fields used in table output)
      const filtered = search
        ? items.filter((item) => {
            return searchableKeys.some((key) =>
              String(item[key] ?? "").toLowerCase().includes(search)
            );
          })
        : items;
    
      if (filtered.length === 0) {
        return { table: "", footer: `No ${label} matching "${options!.search}". Try a different search term.` };
      }
    
      if (filtered.length === 1 && !search) {
        const item = filtered[0];
        const rows = columns.map((column) => `| ${column.header} | ${String(item[column.key] ?? "")} |`);
        return { table: rows.join("\n"), footer: "" };
      }
    
      const total = filtered.length;
      const display = filtered.slice(0, limit);
    
      const headers = ["#", ...columns.map((c) => c.header)];
      const separator = headers.map(() => "---");
      const rows = display.map((item, i) =>
Behavior2/5

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

No annotations provided; description only says 'List available import actions' without mentioning read-only nature, permissions, or side effects.

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, no wasted words, front-loaded with purpose followed by usage guidance.

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?

Lacks return value details (no output schema) and behavioral context; incomplete for a tool with no annotations.

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?

Input schema has 100% coverage with descriptions; description adds no extra meaning beyond schema.

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?

Clearly states verb 'List' and resource 'available import actions in a model'. Distinguishes from siblings by referencing show_importdetails and run_import.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool (to list imports) and directs to alternatives for details and execution.

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