Skip to main content
Glama
HR-Partner

HR Partner MCP Server

Official
by HR-Partner

List Employee Grievances

list_grievances

Retrieve employee grievance and harassment records with type, status, description, and actioned-by. Filter by employee, department, date range, or status to identify and resolve issues promptly.

Instructions

Get employee grievance / complaint / harassment records including type, status, description, actioned-by and reported dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
employeeNoEmployee code to only return records for that particular employee
departmentNoOne or more department names (separated by commas) to filter by
actioned_byNoReturn only records where the 'actioned by' field contains this partial name
descriptionNoReturn only records with this partial text within the description field
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.
grievance_typeNoOnly list records matching this grievance type
grievance_statusNoOnly list records matching this grievance status
reported_date_toNoOnly grievances reported on/before this date (format yyyy-mm-dd)
reported_date_fromNoOnly grievances reported on/after this date (format yyyy-mm-dd)
Behavior3/5

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

With no annotations, the description must carry the transparency burden; it conveys a read-only listing behavior but does not disclose potential limitations such as how filters combine, default return size, or any side effects. It adequately states that records include the listed fields, but lacks depth.

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 concise sentence, front-loaded with the action and resource, with no redundant words. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description, combined with the fully-described schema, gives a basic understanding of the tool's purpose and filters. However, it omits information about default behavior (e.g., returns all grievances when no filters are applied) and does not describe the output structure beyond a few fields, so it is not fully complete.

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 description coverage is 100%, so the baseline is 3. The description lists several response fields that correspond to filter parameters but adds no meaning beyond the schema's own per-parameter descriptions.

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 uses the specific verb 'Get' and clearly identifies the resource as 'employee grievance / complaint / harassment records', which distinguishes this tool from sibling list tools. It also enumerates key fields, making its purpose unmistakable.

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?

No usage guidance is provided. The description does not mention when to use this tool vs alternatives, nor any exclusions or prerequisites, leaving the agent to infer based solely on the tool name.

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