Skip to main content
Glama

show_dimensionitems

List items in an Anaplan dimension and return itemId values needed for write_cells dimension coordinates.

Instructions

List all items in a dimension. Returns itemId values needed for write_cells dimension coordinates. Note: requires model ID (name resolution not supported).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelIdYesAnaplan model ID (name resolution not supported -- use show_models to find the ID)
dimensionIdYesDimension ID (from show_lineitem_dimensions or show_viewdetails)
limitNoMax items to return (default 50, max 1000)
searchNoFilter by name or ID (case-insensitive substring match)

Implementation Reference

  • The tool handler for 'show_dimensionitems' — registers the tool with server.tool, defines the schema (modelId, dimensionId, limit, search), calls apis.dimensions.getAllItems, and returns a formatted table of dimension items (name, code, id).
    server.tool("show_dimensionitems", "List all items in a dimension. Returns itemId values needed for write_cells dimension coordinates. Note: requires model ID (name resolution not supported).", {
      modelId: z.string().describe("Anaplan model ID (name resolution not supported -- use show_models to find the ID)"),
      dimensionId: z.string().describe("Dimension ID (from show_lineitem_dimensions or show_viewdetails)"),
      ...paginationParams,
    }, async ({ modelId, dimensionId, limit, search }) => {
      const items = await apis.dimensions.getAllItems(modelId, dimensionId);
      return tableResult(items, [
        { header: "Name", key: "name" },
        { header: "Code", key: "code" },
        { header: "ID", key: "id" },
      ], "dimension items", { limit, search });
    });
  • Input schema for show_dimensionitems: modelId (string), dimensionId (string), limit (optional number), search (optional string).
    server.tool("show_dimensionitems", "List all items in a dimension. Returns itemId values needed for write_cells dimension coordinates. Note: requires model ID (name resolution not supported).", {
      modelId: z.string().describe("Anaplan model ID (name resolution not supported -- use show_models to find the ID)"),
      dimensionId: z.string().describe("Dimension ID (from show_lineitem_dimensions or show_viewdetails)"),
      ...paginationParams,
    }, async ({ modelId, dimensionId, limit, search }) => {
      const items = await apis.dimensions.getAllItems(modelId, dimensionId);
      return tableResult(items, [
        { header: "Name", key: "name" },
        { header: "Code", key: "code" },
        { header: "ID", key: "id" },
      ], "dimension items", { limit, search });
    });
  • Registration via server.tool("show_dimensionitems", ...) within the registerExplorationTools function (line 77).
    server.tool("show_dimensionitems", "List all items in a dimension. Returns itemId values needed for write_cells dimension coordinates. Note: requires model ID (name resolution not supported).", {
      modelId: z.string().describe("Anaplan model ID (name resolution not supported -- use show_models to find the ID)"),
      dimensionId: z.string().describe("Dimension ID (from show_lineitem_dimensions or show_viewdetails)"),
      ...paginationParams,
    }, async ({ modelId, dimensionId, limit, search }) => {
      const items = await apis.dimensions.getAllItems(modelId, dimensionId);
      return tableResult(items, [
        { header: "Name", key: "name" },
        { header: "Code", key: "code" },
        { header: "ID", key: "id" },
      ], "dimension items", { limit, search });
    });
  • The getAllItems API method that makes the actual HTTP GET call to /models/{modelId}/dimensions/{dimensionId}/items.
    async getAllItems(modelId: string, dimensionId: string) {
      const res = await this.client.get<any>(
        `/models/${modelId}/dimensions/${dimensionId}/items`
      );
      return res.items ?? [];
    }
  • paginationParams shared schema definition used by show_dimensionitems (limit and search fields).
    const paginationParams = {
      limit: z.number().optional().describe("Max items to return (default 50, max 1000)"),
      search: z.string().optional().describe("Filter by name or ID (case-insensitive substring match)"),
    };
Behavior3/5

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

No annotations provided, so description carries full burden. It states it lists items and returns itemIds, but lacks details on side effects, permissions, or rate limits. Adequate but not rich.

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 concise, front-loaded sentences with no wasted words.

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?

No output schema, but description hints at return value. Missing details on pagination, filtering, and error handling. Moderate completeness given parameter count.

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 covers all parameters with descriptions (100% coverage), so description adds little beyond context about itemIds for write_cells. Baseline 3.

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

Purpose4/5

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

Description clearly states 'List all items in a dimension' and mentions its use for write_cells, but does not differentiate from sibling lookup_dimensionitems.

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

Usage Guidelines3/5

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

Implies usage through note about model ID requirement and mention of write_cells, but no explicit when-to-use or alternatives.

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