Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

getContractBillingCycles

getContractBillingCycles

Retrieves a contract's billing cycles to identify the exact date range for invoice generation. Required before calling generateInvoice to ensure accurate billing.

Instructions

Returns the contract's pre-computed billing cycles as a list of {name, start_date, end_date, bill_for_date, billing_cycle_start_day}. REQUIRED before calling generateInvoice. Workflow: (1) call this tool, (2) pick the cycle entry whose date range covers the period you want to invoice, (3) pass that entry's start_datefrom_date, end_dateto_date, bill_for_date, billing_cycle_start_day to generateInvoice — copy the values verbatim, no math. The backend matches bill_for_date exactly against this list; arbitrary dates produce empty invoice arrays.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contractIdYesThe unique identifier (UUID) of the contract.
limitNoMaximum number of cycles to return (default 10). Increase if the contract spans many years.
__userContextNoInternal user context for multi-tenant authentication and approval workflow
Behavior4/5

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

With no annotations, the description discloses that the tool returns pre-computed cycles and that the backend requires exact match on bill_for_date. Implies read-only behavior, though could mention 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?

Concise yet detailed, front-loading purpose and providing step-by-step workflow. Every sentence serves a purpose with no unnecessary information.

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

Completeness5/5

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

Fully explains output format, required inputs, and integration with generateInvoice. Despite no output schema, the workflow is clearly documented, making it contextually complete.

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 coverage is 100%, so the schema documents each parameter. The description adds context for 'limit' but little beyond schema for others. Baseline 3 is appropriate.

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 explicitly states it returns billing cycles as a list of specific fields and distinguishes itself from siblings like generateInvoice by being a prerequisite step.

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?

It provides a clear workflow: call before generateInvoice, pick a cycle, and pass values verbatim. It warns against using arbitrary dates, giving explicit guidance on when and how to use.

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/zenskar/mcp-zenskar'

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