Skip to main content
Glama
HR-Partner

HR Partner MCP Server

Official
by HR-Partner

List Employee Skills

list_skills

Retrieve employee skill records with skill name, rating, and comments. Filter by employee, department, skill name, rating range, or comment text to analyze workforce competencies.

Instructions

Get employee skill records including skill name, rating and comments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commentsNoReturn only skill records 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
skill_nameNoReturn all skills which have this name
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.
skill_ratingNoReturn all skills which have this rating
skill_rating_toNoReturn all skills with a rating at or below this value (numeric or text rating)
skill_rating_fromNoReturn all skills with a rating at or above this value (numeric or text rating)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that records are retrieved, but does not disclose whether filtering is supported, whether pagination occurs, or any permissions are needed. The schema hints at filtering, but the description does not confirm or explain these behaviors, leaving the agent uncertain about how the tool will behave.

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 of 10 words, front-loaded with the core purpose. It contains no filler or redundant information, making it highly concise while still conveying the essential action and resource.

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?

Given the tool's moderate complexity (8 optional parameters, no output schema, no annotations), the description is minimal but adequate. It tells the agent what data is returned, but does not mention that the tool supports filtering or that it returns a list (though 'records' implies plural). The parameter schema covers the filtering options, so the description does not need to repeat them, but it could be more complete by stating that records can be filtered and that multiple records may be returned.

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 input schema already fully documents all 8 parameters. The description adds no additional parameter semantics; it only mentions output fields (skill name, rating, comments), which are not parameter descriptions. Thus the baseline of 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 tool's function: 'Get employee skill records including skill name, rating and comments.' The verb 'Get' and resource 'employee skill records' are specific, and the mention of fields (skill name, rating, comments) distinguishes it from other list tools in the sibling set, which focus on different domains (absences, assets, benefits, etc.).

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. It does not mention exclusions, prerequisites, or suggest sibling tools for related queries (e.g., employee details). Usage is only implied by the tool's name and description, which is insufficient given the large sibling set.

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