Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

List Org Users

list_org_users
Read-onlyIdempotent

Retrieve a paginated list of all users in the organization with sorting and cursor-based navigation.

Instructions

List all users in the Coalesce organization.

Args:

  • limit, startingFrom, orderBy, orderByDirection: Pagination controls

Returns: { data: User[], next?: string, total?: number }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (max 500)
orderByNoField to sort by (required with startingFrom)
startingFromNoCursor from previous response's next field
orderByDirectionNoSort direction

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
nextNo
totalNo
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds pagination details and return type, which are behavioral traits beyond annotations. However, it does not mention rate limits, data freshness, or any potential delays.

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 extremely concise, using only a few lines to cover purpose, parameters, and return type. Every sentence is informative with no redundancy.

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?

Given the low complexity, rich annotations, complete schema, and presence of output schema, the description is adequate. It covers the essential aspects (purpose, pagination, return shape). However, it could mention that the list includes all users regardless of status.

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?

The input schema has 100% description coverage for all parameters. The description only lists parameter names and groups them as 'Pagination controls', adding minimal value beyond the schema. 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 clearly states the verb 'List' and the resource 'users in the Coalesce organization'. It is distinct from sibling tools like 'cache_org_users' which implies a caching operation, and 'list_user_roles' which lists roles per user. The scope 'organization' is specific.

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?

The description implies usage for listing users with pagination but does not explicitly state when to use this tool over alternatives (e.g., 'cache_org_users' might be for cached results). No when-not-to-use or exclusion criteria are provided, leaving the agent to infer from context.

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/Coalesce-Software-Inc/coalesce-transform-mcp'

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