Skip to main content
Glama
HR-Partner

HR Partner MCP Server

Official
by HR-Partner

List Expense Claims

list_expenses

Retrieve employee expense claims with detailed, summary, or transaction report types. Filter by status, employee, project, department, date ranges, and more for targeted results.

Instructions

Get employee expense claims. The report_type controls the shape: 'detailed' returns claim headers plus expense lines and attachments, 'summary' returns claim headers only, 'transaction' returns expense lines only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoOnly claims with this status
is_paidNoFilter claims on whether they have been paid (true/false)
projectNoThe project name to filter by
employeeNoEmployee code to only return records for that particular employee
locationNoOne or more location names (separated by commas) to filter by
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.
report_typeYesRequired. 'detailed' = claim headers + lines + attachments; 'summary' = claim headers only; 'transaction' = expense lines only
expense_date_toNoOnly expenses dated on/before this date (format yyyy-mm-dd)
approved_date_toNoOnly claims approved on/before this date (format yyyy-mm-dd)
expense_categoryNoThe expense category name to filter by
expense_date_fromNoOnly expenses dated on/after this date (format yyyy-mm-dd)
submitted_date_toNoOnly claims submitted on/before this date (format yyyy-mm-dd)
approved_date_fromNoOnly claims approved on/after this date (format yyyy-mm-dd)
submitted_date_fromNoOnly claims submitted on/after this date (format yyyy-mm-dd)
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the response shape depends on report_type, which is a key behavioral trait. It doesn't mention pagination or default return size, but the schema's max_records description already covers the no-pagination behavior, so the description adds value beyond schema.

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?

Two concise sentences, first stating purpose, second explaining the key parameter. No wasted words.

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

Completeness4/5

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

Given the tool has 15 parameters and no output schema, the description does not summarize the filter capabilities, but the schema provides comprehensive parameter descriptions. The description's focus on report_type gives essential clarity for the required parameter, making it adequate for the 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no new parameter semantics beyond restating the report_type enum values, which are already fully described in 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's function with a specific verb ('Get') and resource ('employee expense claims'), distinguishing it from sibling list_* tools by focusing on the expense domain. It additionally explains the three report_type shapes, which clarifies the tool's scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for choosing a report_type, explaining what each variant returns. It doesn't name any alternative tools for expense claims, but since no expense-specific sibling exists, this is sufficient context without explicit exclusions.

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