Skip to main content
Glama
Sign In
HR Assistant MCP Agent

HR Assistant MCP Agent

by sachink1712
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_leave_balance

Check an employee's leave balance using their employee ID to support accurate leave management and planning.

Instructions

Get the leave balance of an employee.
Args:
    emp_id: str
Returns:
    str

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "emp_id": "<emp_id>"
    },
    "name": "get_leave_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
emp_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It only states that the tool gets a balance and returns a string; it does not disclose read-only guarantees, error behavior, what the string represents, or the effect of an invalid employee ID.

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

Conciseness4/5

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

The description is compact and follows an Args/Returns structure that is easy to scan. It contains a small amount of redundancy with the schema, but it is not bloated.

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 one-parameter read-style tool, the description is minimally sufficient: it states the purpose and the argument. However, it lacks sibling differentiation and edge-case behavior, which matters because an output schema exists but no guidance is given for selecting this tool over get_leave_history.

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

Parameters2/5

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

Schema description coverage is 0%, but the description repeats only the parameter name and type ('emp_id: str') without adding meaning. The phrase 'of an employee' lightly implies emp_id identifies an employee, but no format, source, or validation details are given.

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

Purpose4/5

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

Description uses a specific verb ('Get') and resource ('leave balance of an employee'), clearly identifying what the tool returns. It is distinguishable from siblings like get_leave_history and apply_leave, though it does not explicitly call out the distinction.

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 guidance is given about when to use this tool versus sibling tools such as get_leave_history or apply_leave. The usage context must be inferred entirely from the tool name and the generic 'Get' phrasing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools