Skip to main content
Glama
HR-Partner

HR Partner MCP Server

Official
by HR-Partner

List Employee Dependents

list_dependents

Retrieves employee dependents and next-of-kin records, including type, name, contact details, and date of birth. Supports filtering by employee, department, dependent type, and more.

Instructions

Get employee dependent / next-of-kin records including type, name, contact details and date of birth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoReturn only dependents with this partial text within the name field
commentsNoReturn only dependents with this partial text within the comments field
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.
dependent_typeNoOnly list records matching this dependent type
contact_detailsNoReturn only dependents with this partial text within the contact details field
date_of_birth_toNoOnly dependents born on/before this date (format yyyy-mm-dd)
date_of_birth_fromNoOnly dependents born on/after this date (format yyyy-mm-dd)
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It only restates the resource and fields, adding no information about read-only guarantees, pagination, filtering scope, or permissions. The schema notes the lack of pagination, but the description itself is silent on behavior.

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 sentence, front-loaded with the action and resource, with no unnecessary words.

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?

For a read/list tool with no output schema, the description gives minimal return info (fields included) but leaves behavioral details to the schema. It is adequate for basic understanding but could be more complete regarding result format and limitations.

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?

All 9 parameters have schema descriptions (100% coverage), so the description adds no extra parameter semantics. The description mentions fields returned but does not elaborate on parameter usage or constraints beyond the schema.

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 gets dependent/next-of-kin records, listing the fields returned (type, name, contact details, date of birth). It is distinct from sibling tools, none of which specifically target dependents.

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 use for listing dependent records, but provides no explicit guidance on when to use this tool versus alternatives or when not to use it. The context is clear, but no exclusions or alternative tools are mentioned.

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