Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

createContract

createContract

Create a new contract in Zenskar with customer details, pricing phases, products, and billing configuration.

Instructions

Create a new contract in Zenskar. Use this after extracting contract data via extractContractFromRaw and creating a customer via createCustomer. The contract includes customer details, pricing phases, products, and billing configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesContract name (required).
descriptionNoContract description (optional).
statusNoContract status (required, typically 'draft' for new contracts).draft
currencyNoCurrency code for the contract (e.g., 'USD', 'EUR').USD
start_dateYesContract start date in ISO 8601 format (e.g., '2025-01-01T00:00:00.000000').
end_dateNoContract end date in ISO 8601 format (e.g., '2025-12-31T23:59:59.999999'). Optional — omit for open-ended contracts.
anchor_dateNoAnchor date for billing cycles in ISO 8601 format (defaults to start_date).
customer_idYesThe ID of the customer for this contract (required, UUID format).
renewal_policyNoContract renewal policy. Currently only 'do_not_renew' is supported at runtime.do_not_renew
bill_parent_customerNoWhether to bill the parent customer (defaults to false).
phasesNoArray of contract phases with pricing details. Each phase includes name, start_date, end_date, phase_type, and pricings array. Defaults to empty array if omitted.
sourceNoSource information for the contract (e.g., {source_type: 'ai', source_id: 'uuid'}).
custom_attributesNoCustom attributes for the contract as key-value pairs.
__userContextNoInternal user context for multi-tenant authentication and approval workflow
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'Create a new contract' without disclosing behavioral traits such as potential failure conditions, authentication requirements, or what happens on success. Lacks detail on side effects or constraints.

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?

Three sentences with no redundancy: first sentence states purpose, second gives usage guidance, third lists included components. Well-structured and front-loaded.

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

Completeness2/5

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

Given the tool's complexity (14 parameters, nested objects, no output schema), the description lacks completeness. It does not explain return values, provide examples, or clarify how to structure phases. The schema helps, but the description should offer more contextual guidance.

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% with individual parameter descriptions, so baseline is 3. The description adds minimal extra meaning beyond summarizing components like 'customer details, pricing phases, products, and billing configuration', which is already implied by the schema.

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 verb 'Create a new contract' and resource 'in Zenskar', and distinguishes from sibling tools like createCustomer and createContractPhase by providing prerequisites. It also lists what the contract includes, making 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 Guidelines4/5

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

Explicitly guides agents to use this after extractContractFromRaw and createCustomer, providing a clear workflow order. However, does not mention when not to use it or alternatives for contract modifications, but for a creation tool this is sufficient.

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