Skip to main content
Glama
ArmandSwirc

TimeChimp MCP Server

by ArmandSwirc

get_users

Retrieve user data from TimeChimp with pagination, filtering, and sorting options for managing team access and permissions.

Instructions

Retrieve all users from TimeChimp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMaximum number of users to return (1-10000, default: 100)
skipNoNumber of users to skip for pagination (default: 0)
countNoWhether to include the total count of results (default: true)
expandNoComma-delimited list of properties to expand
active_onlyNoOnly return active users (default: false)
filterNoOData filter expression (e.g., "firstName eq 'John'" or "active eq true")
orderbyNoOData orderby expression (e.g., "firstName asc" or "lastName desc")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Retrieve' implies a read operation, it doesn't mention pagination behavior (implied by skip/top parameters), rate limits, authentication requirements, or what format the results will be returned in. The description is minimal and lacks important operational context.

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 - a single sentence that states the core purpose without any fluff. It's front-loaded with the essential information and wastes no words, though this conciseness comes at the cost of completeness.

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?

For a tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'users' means in this context, what fields are returned, how results are structured, or provide any examples. The minimal description leaves too much undefined for a tool with this complexity.

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 with detailed parameter documentation, so the baseline is 3. The description adds no additional parameter context beyond what's already in the schema properties, but doesn't need to since the schema is comprehensive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Retrieve') and resource ('all users from TimeChimp'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'get_user_by_id' or explain what 'all users' means in context of the filtering parameters available.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_user_by_id' or other get_* tools. There's no mention of prerequisites, typical use cases, or when this bulk retrieval approach is preferred over individual lookups.

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/ArmandSwirc/TimeChimpMCP'

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