Skip to main content
Glama

xero_list_payroll_au_employee_leave_balances

Retrieve leave balances for Australian employees in Xero Payroll. View accrued annual, sick, and other leave types per employee.

Instructions

Xero connector operation list_payroll_au_employee_leave_balances (platform tool xero.list_payroll_au_employee_leave_balances).

Routes through /api/tools/invoke under your JWT, tenant, and company scope.

Args: arguments: JSON string of arguments for the connector operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo{}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

No annotations are provided, and the description discloses no behavioral traits such as read-only nature, side effects, permissions, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but contains mostly procedural routing details that are not helpful for an agent. It is under-specified rather than efficiently concise.

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

Completeness1/5

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

Even though an output schema exists, the description does not mention what data is returned. For a payroll leave balance listing tool, this is critically incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. The description only states the 'arguments' parameter is a JSON string, adding no information about expected keys, valid values, or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description merely repeats the tool name and provides routing info, but fails to explain what listing leave balances means. It does not differentiate from sibling tools like xero_list_payroll_au_employees.

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

Usage Guidelines1/5

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

No guidance on when or why to use this tool. The description focuses on technical routing rather than usage context or alternatives.

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/RPasquale/lightbulb-mcp'

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