Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

listEntitlements

listEntitlements

Retrieve paginated entitlements with filters by ID, name, type, product, and active status. Manage permissions and access efficiently.

Instructions

List entitlements in paginated form, with filtering by ID, name, type, product, and active status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoThe cursor for pagination.
limitNoMaximum number of records to return per page (defaults to 50).
orderNoOrder of results (e.g., '-created_at').-created_at
sort_keyNoKey to sort the results by.created_at
sort_typeNoSort order type ('ASC' or 'DESC').DESC
searchNoText search across entitlement fields.
idNoFilter by entitlement ID.
name__ilikeNoCase-insensitive partial match for entitlement name.
entitlement_typeNoFilter by entitlement type.
is_activeNoFilter by active status.
product_idNoFilter by associated product ID.
__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 carries the full burden but only mentions pagination and filters. It fails to disclose behavioral traits like default limit, sort behavior, or any 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 a single, efficient sentence that conveys the core functionality without wasted words.

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?

Despite 12 parameters and no output schema, the description omits important details like return format, pagination cursor usage, and ordering behavior, leaving gaps for the agent.

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 baseline 3 applies. The description simply summarizes the filter fields without adding further meaning or usage notes beyond what the schema already provides.

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 lists 'entitlements in paginated form' with specific filtering options, effectively differentiating it from single-entitlement retrieval or mutation tools.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance is provided. The context of sibling list tools implies general usage for multiple entitlements, but no alternatives are mentioned.

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