Skip to main content
Glama

show_modules

List all modules in an Anaplan model. Filter by name or ID to find specific modules, and control the number of results returned.

Instructions

List all modules in a model. Use show_lineitems to see a module's line items, or show_savedviews to find views for read_cells.

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

  • Handler for show_modules tool. Resolves workspace/model IDs, calls apis.modules.list(), and formats results as a table with name/ID columns and next-step hints.
    server.tool("show_modules", "List all modules in a model. Use show_lineitems to see a module's line items, or show_savedviews to find views for read_cells.", {
      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 modules = await apis.modules.list(wId, mId);
      return withNextSteps(
        tableResult(modules, [{ header: "Name", key: "name" }, { header: "ID", key: "id" }], "modules", { limit, search }),
        ["Use show_lineitems to see line items, show_savedviews for views, or show_moduledetails for dimension layout."],
      );
    });
  • Registration of the show_modules tool via server.tool() inside registerExplorationTools().
    server.tool("show_modules", "List all modules in a model. Use show_lineitems to see a module's line items, or show_savedviews to find views for read_cells.", {
      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 modules = await apis.modules.list(wId, mId);
      return withNextSteps(
        tableResult(modules, [{ header: "Name", key: "name" }, { header: "ID", key: "id" }], "modules", { limit, search }),
        ["Use show_lineitems to see line items, show_savedviews for views, or show_moduledetails for dimension layout."],
      );
    });
  • Schema definition for show_modules: workspaceId (string), modelId (string), limit (optional number), search (optional string).
    server.tool("show_modules", "List all modules in a model. Use show_lineitems to see a module's line items, or show_savedviews to find views for read_cells.", {
      workspaceId: z.string().describe("Anaplan workspace ID or name"),
      modelId: z.string().describe("Anaplan model ID or name"),
      ...paginationParams,
  • ModulesApi.list() - fetches all modules for a model via the Anaplan REST API. Used by show_modules handler.
    async list(workspaceId: string, modelId: string) {
      return this.client.getAll<any>(
        `/workspaces/${workspaceId}/models/${modelId}/modules`, "modules"
      );
  • Export function that registers the show_modules tool (among others) on the MCP server.
    export function registerExplorationTools(server: McpServer, apis: ExplorationApis, resolver: NameResolver) {
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions 'List' implying a read-only operation but does not explicitly state safety, pagination behavior, or other traits. Adequate but minimal.

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 with no waste. The main action is front-loaded, and usage guidance is provided concisely.

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

Completeness4/5

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

Given the tool's simplicity, no output schema, and no annotations, the description is fairly complete: it states the purpose, provides alternatives, and the schema covers parameters. Could mention response format, but not essential for this type of tool.

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 baseline is 3. The description does not add meaning beyond what the schema provides for parameters; it only lists the tool's function.

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 'List all modules in a model' with a specific verb and resource. It also distinguishes from siblings (show_lineitems, show_savedviews), making the tool's purpose unambiguous.

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?

The description explicitly tells when to use alternatives: 'Use show_lineitems to see a module's line items, or show_savedviews to find views for read_cells.' This provides clear guidance on when not to use this tool.

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