Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

listContracts

listContracts

Retrieve a paginated list of contracts with filters for ID, customer, name, start/end dates, creation date, and status.

Instructions

Retrieve a paginated list of contracts, with extensive options for filtering by ID, customer ID, name, start date, end date, creation date, and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoThe cursor for pagination to fetch the next or previous set of records.
limitNoMaximum number of records to return per page (defaults to 10).
orderNoOrder of results (e.g., '-created_at' for descending creation date).-created_at
idNoFilter by Contract ID (exact match).
id__inNoFilter by a comma-separated list of Contract IDs.
id__isnullNoFilter by whether Contract ID is null.
customer_idNoFilter by Customer ID (exact match).
customer_id__inNoFilter by a comma-separated list of Customer IDs.
customer_id__isnullNoFilter by whether Customer ID is null.
nameNoFilter by Contract Name (exact match).
name__ilikeNoContract Name (case-insensitive partial match).
name__likeNoContract Name (case-sensitive partial match).
name__inNoFilter by a comma-separated list of Contract Names.
name__isnullNoFilter by whether Contract Name is null.
start_dateNoContract Start Date (exact match, ISO 8601).
start_date__neqNoContract Start Date (not equal, ISO 8601).
start_date__gtNoContract Start Date (greater than, ISO 8601).
start_date__gteNoContract Start Date (greater than or equal to, ISO 8601).
start_date__ltNoContract Start Date (less than, ISO 8601).
start_date__lteNoContract Start Date (less than or equal to, ISO 8601).
start_date__isnullNoFilter by whether Contract Start Date is null.
start_date__inNoFilter by a comma-separated list of Contract Start Dates.
created_atNoContract Created At (exact match, ISO 8601).
created_at__neqNoContract Created At (not equal, ISO 8601).
created_at__gtNoContract Created At (greater than, ISO 8601).
created_at__gteNoContract Created At (greater than or equal to, ISO 8601).
created_at__ltNoContract Created At (less than, ISO 8601).
created_at__lteNoContract Created At (less than or equal to, ISO 8601).
created_at__isnullNoFilter by whether Contract Created At is null.
created_at__inNoFilter by a comma-separated list of Contract Creation Dates.
end_dateNoContract End Date (exact match, ISO 8601).
end_date__neqNoContract End Date (not equal, ISO 8601).
end_date__gtNoContract End Date (greater than, ISO 8601).
end_date__gteNoContract End Date (greater than or equal to, ISO 8601).
end_date__ltNoContract End Date (less than, ISO 8601).
end_date__lteNoContract End Date (less than or equal to, ISO 8601).
end_date__isnullNoFilter by whether Contract End Date is null.
end_date__inNoFilter by a comma-separated list of Contract End Dates.
statusNoFilter contracts by their status.
status__inNoFilter by a comma-separated list of contract statuses.
__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?

With no annotations, the description should disclose behavioral traits like pagination, sort order, or side effects. It only mentions 'paginated' and 'filtering options' but lacks details on rate limits, authentication, or what happens with no results. Being a read operation is implied but not confirmed.

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 a single sentence that efficiently states the tool's purpose. It is front-loaded with the main action and avoids unnecessary words. Every piece of information earns its place.

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 large number of parameters (41) and no output schema, the description is insufficient. It does not explain pagination mechanics (cursor usage), ordering behavior, or the structure of returned contracts. The tool's complexity demands more context.

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 description coverage is 100%, so the schema already documents all 41 parameters. The description adds no additional meaning beyond listing field groups (ID, customer, name, etc.). This meets the baseline for high schema coverage but does not enhance understanding.

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 retrieves a paginated list of contracts and lists common filter fields. This distinguishes it from sibling tools like getContractById (single contract) or createContract. The verb 'retrieve' and resource 'list of contracts' are specific.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., getContractById for a single contract, or listInvoices for invoices). The description does not mention when not to use it or prerequisites.

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