Skip to main content
Glama
larasrinath

Anaplan MCP

by larasrinath
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

write_cells

Write values to Anaplan cells using IDs or names to define line items and dimensions. Update specific cell values with numbers, strings, or booleans.

Instructions

Write values to specific cells. Supports both ID-based and name-based targeting: use lineItemName/dimensionName/itemName instead of IDs to skip the dimension resolution chain. For ID-based writes, use show_lineitem_dimensions then show_dimensionitems.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesAnaplan workspace ID or name
modelIdYesAnaplan model ID or name
moduleIdYesModule ID or name
dataYesCell values to write. Supports both ID-based and name-based targeting.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed15 schema fields changedv1.2.0
    • changedInput schema / properties / data / description
      Previous value: -"Array of cell values to write"New value: +"Cell values to write. Supports both ID-based and name-based targeting."
    • removedInput schema / properties / data / items / properties / dimensions / additionalProperties
      Removed value: -{
-  "type": "string"
-}
    • changedInput schema / properties / data / items / properties / dimensions / description
      Previous value: -"Dimension member names keyed by dimension name"New value: +"Dimension coordinates (use IDs or names)"
    • addedInput schema / properties / data / items / properties / dimensions / items
      Added value: +{
+  "properties": {
+    "dimensionId": {
+      "description": "Dimension ID (from show_lineitem_dimensions)",
+      "type": "string"
+    },
+    "dimensionName": {
+      "description": "Dimension name (alternative to dimensionId)",
+      "type": "string"
+    },
+    "itemCode": {
+      "description": "Item code (alternative to itemId/itemName)",
+      "type": "string"
+    },
+    "itemId": {
+      "description": "Item ID (from show_dimensionitems)",
+      "type": "string"
+    },
+    "itemName": {
+      "description": "Item name (alternative to itemId)",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / data / items / properties / dimensions / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • changedInput schema / properties / data / items / properties / dimensions / type
      Previous value: -"object"New value: +"array"
    • addedInput schema / properties / data / items / properties / lineItemId
      Added value: +{
+  "description": "Line item ID (from show_lineitems)",
+  "type": "string"
+}
    • addedInput schema / properties / data / items / properties / lineItemName
      Added value: +{
+  "description": "Line item name (alternative to lineItemId)",
+  "type": "string"
+}
    • addedInput schema / properties / data / items / properties / value / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
    • removedInput schema / properties / data / items / properties / value / type
      Removed value: -"string"
    • removedInput schema / properties / lineItemId
      Removed value: -{
-  "description": "Line item ID to write to",
-  "type": "string"
-}
    • changedInput schema / properties / modelId / description
      Previous value: -"Anaplan model ID"New value: +"Anaplan model ID or name"
    • changedInput schema / properties / moduleId / description
      Previous value: -"Module ID"New value: +"Module ID or name"
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Anaplan workspace ID"New value: +"Anaplan workspace ID or name"
    • changedInput schema / required
      Previous value: -[
-  "workspaceId",
-  "modelId",
-  "moduleId",
-  "lineItemId",
-  "data"
-]New value: +[
+  "workspaceId",
+  "modelId",
+  "moduleId",
+  "data"
+]
  2. Addedv0.1.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'write values', which indicates mutation, but lacks details on rate limits, authentication requirements, 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?

The description is two sentences, front-loads the purpose, and provides additional detail without unnecessary verbiage.

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?

For a write operation with no output schema, the description should clarify return behavior (e.g., success/error responses) and constraints on value types. It is adequate but lacks completeness.

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

Parameters4/5

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

Schema coverage is 100%, and the description adds value by explaining the dual targeting strategy (name-based vs ID-based), which goes beyond the schema descriptions.

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 tool writes values to cells and distinguishes between ID-based and name-based targeting, setting it apart from read-only tools like read_cells.

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?

The description provides explicit guidance on when to use name-based vs ID-based targeting and mentions prerequisite tools for ID-based writes, but does not explicitly state 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