Skip to main content
Glama
ShahjahanAliTaimoor

kiwi-tcms-mcp

by ShahjahanAliTaimoor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

kiwi_get_users

List Kiwi users with optional filters such as username or email. Requires the auth.view_user permission; without it, authentication fails with error -32098.

Instructions

List Kiwi users. Filter e.g. {"username": "sqa1"} or {"email__icontains": "acme.com"}. Requires the 'auth.view_user' permission on your Kiwi account; without it Kiwi returns error -32098 ("Authentication failed").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoKiwi ORM filter dict, e.g. {"name": "My Product"} or {"product_id": 3}. Omit or pass {} to list everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does well by naming the required permission and the exact error/code returned when it is missing. It could also mention read-only semantics or return shape, but the permission/error detail is substantive.

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 two sentences with no filler. It front-loads the purpose, then adds filter examples and a permission warning, each sentence earning its place.

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?

For a one-optional-parameter read tool, the description covers purpose, filter syntax, permission requirements, and failure behavior. The main gap is the absence of explicit return-value or pagination details, which is more noticeable because no output schema or annotations are provided.

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 covers the query parameter generically with 100% coverage, giving a baseline of 3. The description adds value by providing user-specific filter examples ('username', 'email__icontains') that are not present in the schema's generic product-oriented example.

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 opens with 'List Kiwi users', a clear verb and resource, and the filter examples confirm it returns user records. The 'users' resource is unambiguous and no sibling tool handles users, so it is well differentiated.

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?

The tool's intended use is immediately apparent: list Kiwi users with optional filtering. It provides practical filter patterns and a permission prerequisite, though it does not explicitly compare against sibling getter tools or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools