Skip to main content
Glama
HR-Partner

HR Partner MCP Server

Official
by HR-Partner

List Reminders

list_reminders

Get admin reminders with description, module, remind date, and notification flags. Filter by responsible user, employee, department, or module to find specific entries.

Instructions

Get admin reminders with description, module, remind date, notification flags and the responsible user/employee.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoOnly reminders where the responsible admin user has this email address
activeNoFilter by the active flag (true/false)
moduleNoOnly reminders belonging to this module (e.g. training, note, review)
employeeNoEmployee code to only return records for that particular employee
departmentNoOne or more department names (separated by commas) to filter by
max_recordsNoOptional client-side limit on the number of records returned. Use to keep responses small when exploring data; the API itself does not paginate.
notification_sentNoFilter by the notification_sent flag (true/false)
send_notificationNoFilter by the send_notification flag (true/false)
Behavior2/5

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

There are no annotations provided, so the description carries the full burden for behavioral disclosure. The description only states the output fields and does not mention that this is a read-only list operation, that it returns multiple records, or that filtering is available. It also fails to disclose any limitations like pagination (though max_records param hints at it). This is a significant gap for a list tool.

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, tightly worded sentence with no filler. It front-loads the resource ('admin reminders') and then lists the key attributes returned. It is appropriately concise for the information it conveys.

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?

With no annotations and no output schema, the description should more thoroughly explain the tool's behavior. It does not mention that it returns a list, that filters are available, or how it differs from get_reminder. For a tool with 8 optional parameters and sibling tools, this description is under-specified.

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 8 parameters, so the schema already explains each filter. The description adds minimal value by naming some output fields, but it does not clarify that all parameters are optional filters or provide any additional context beyond the schema. Baseline of 3 applies.

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 admin reminders and specifies key attributes returned (description, module, remind date, notification flags, responsible user/employee). The verb 'Get' is specific, and the plural 'reminders' distinguishes it from sibling tools like get_reminder which retrieves a single record.

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 provides a clear statement of what the tool does, implying it is for fetching a list of reminders. However, it does not explicitly mention when to use this vs. alternatives such as get_reminder for a single reminder, nor does it note any prerequisites or exclusions. Usage is inferred from the name and description but not explicitly guided.

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/HR-Partner/hrpartner-mcp'

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