HR-ASSIST

Overview Schema Source Related Servers Discussions Admin

create_ticket

Submit a purchase request ticket for an employee's required item, specifying employee ID, item, and reason, to initiate HR procurement approval.

Instructions

Create a ticket for buying required items for an employee.
:param emp_id: Employee ID
:param item: Item requested (Laptop, ID Card, etc.)
:param reason: Reason for the request
:return: Confirmation message

Input Schema

TableJSON Schema

Name	Required	Description	Default
`item`	Yes
`emp_id`	Yes
`reason`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only mentions that a confirmation message is returned; it says nothing about required permissions, whether the ticket can be modified or cancelled afterward, or any side effects on the employee record.

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?

Short and front-loaded, with the core purpose in the first sentence. The Sphinx-style :param: lines partially duplicate the schema but are justified given the 0% schema coverage.

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?

An output schema exists, so return values need not be explained. Parameters are minimally covered, but for a mutation tool with no annotations the description leaves behavioral gaps (permissions, reversibility, downstream effects on the ticket lifecycle).

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 0%, so the description's param notes are the only semantics available, and they do add value — especially 'item' with examples like Laptop and ID Card. However, emp_id and reason are restated almost verbatim from their titles, so the added meaning is thin.

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?

States a specific verb and resource ('Create a ticket') plus the domain scope ('for buying required items for an employee'). It does not differentiate from siblings like list_tickets or update_ticket_status, but the creation intent is unambiguous.

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 on when to use this versus list_tickets or update_ticket_status, and no prerequisites (e.g., must the employee already exist). Usage must be inferred purely from the purpose statement.

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

Deploy Server