Skip to main content
Glama

create_date_table

Create a complete Power BI date table in one call, including year, quarter, month, and hierarchy. Size it to your fact dates or generate offline PBIP TMDL.

Instructions

Create a fully-formed date table in ONE call: Date, Year, Quarter, Month, MonthYear + sort-by columns + a Year>Quarter>Month hierarchy. Then relate your fact's date column to [Date]. Pass dateColumnRef (e.g. "Fact[Date]") to size the range to your data, else CALENDARAUTO() is used. target=pbip: pass pbipFolder instead of sessionId to write the SAME table as Desktop-faithful TMDL into a PBIP semantic model with NO engine (columns authored explicitly; data materialises on the first Desktop refresh).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNotable name, e.g. CalendarCalendar
hierarchyNoalso build a Year>Quarter>Month hierarchy
sessionIdNosessionId from connect_model (live engine; pass exactly one of sessionId / pbipFolder)
pbipFolderNotarget=pbip: a PBIP <name>.SemanticModel / TMDL definition folder to edit OFFLINE (engine-free)
dateColumnRefNodate column to size the range, e.g. Fact_Sales[Week Ending] (optional)
Behavior4/5

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

With no annotations, the description carries the full burden and covers key behavioral traits: creating the complete table in one call, using CALENDARAUTO when no dateColumnRef is given, and the offline PBIP mode with no engine and first-refresh materialization. It lacks details on overwrite/error behavior, but is still substantially transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, front-loaded with the core purpose. Each sentence covers a distinct aspect: creation output, relationship step, range sizing, and PBIP mode. It is dense but efficient, with no filler words.

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 5 parameters and no output schema, the description covers the main functionality, two deployment modes, parameter interactions, and a necessary follow-up action (relating the date column). It omits sort-by column names and overwrite behavior, but these are not critical for a creation tool.

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?

The schema already documents all parameters, but the description adds valuable meaning: mutual exclusivity of sessionId and pbipFolder, how dateColumnRef sizes the range with an example, and the 'SAME table' guarantee for pbipFolder. This decision logic goes beyond the schema's individual field 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 creates a full date table with specified columns (Date, Year, Quarter, Month, MonthYear), sort-by columns, and a hierarchy. It distinguishes itself from siblings by emphasizing 'in ONE call' and the specific PBIP offline mode, making the tool's unique value explicit.

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 guidance on when to use dateColumnRef vs CALENDARAUTO, and the choice between sessionId and pbipFolder for different target scenarios. It does not compare directly with alternative tools, but offers strong within-tool usage context and a post-creation relationship step.

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/cyphonica/powerbi-pbix-mcp'

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