Skip to main content
Glama
kula-ai

@kula-ai/mcp-server

Official
by kula-ai

create_requisition

Create a new job requisition with role, employment type, and department. Automatically generates linked requisitions when head count exceeds 1.

Instructions

Create a new requisition. When head_count exceeds 1, creates a group of linked requisitions. Use list_requisition_fields to get available custom field IDs for additional_info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_nameYesJob role name for this requisition
employment_typeYesEmployment type (full_time, part_time, contract, internship, temporary, seasonal)
requisition_typeYesRequisition type (new_hire, contract, backfill, internship, internal)
department_idYesDepartment ID
office_idsYesComma-separated office IDs (at least one required)
descriptionNoRequisition description
minimum_salaryNoMinimum salary amount
maximum_salaryNoMaximum salary amount
salary_currency_idNoCurrency country ID for salary
recruiter_idNoUser ID of the assigned recruiter
hiring_manager_idNoUser ID of the hiring manager
target_hire_dateNoTarget hire date (YYYY-MM-DD)
target_start_dateNoTarget start date (YYYY-MM-DD, must be on or after target_hire_date)
head_countNoNumber of positions (1–50). Set greater than 1 to generate multiple linked requisitions
confidentialNoWhether this requisition is confidential
job_idNoJob ID to associate with this requisition
additional_infoNoCustom fields as key-value pairs (field ID to value). Use list_requisition_fields to get field IDs.
Behavior3/5

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

Describes that exceeding head_count of 1 creates linked requisitions, which is key behavior. However, no annotations are provided, and the description does not cover permissions, rate limits, or response behavior, leaving gaps.

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 succinct sentences that immediately convey the action and a key nuance. No wasted words; front-loaded with purpose.

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?

Adequately explains core behavior and references a related tool for custom fields. Lacks return value details and prerequisites, but given complexity (17 params, no output schema) it is mostly complete.

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 descriptions cover all 17 parameters (100% coverage), so the description adds no additional parameter meaning beyond the schema. Baseline of 3 applies.

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?

Clearly states 'Create a new requisition' and explains the linked requisitions behavior when head_count > 1. Distinguishes from sibling tools like close_requisition and update_requisition.

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

Usage Guidelines3/5

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

Provides a hint to use list_requisition_fields for custom field IDs, but no explicit guidance on when to use this tool vs alternatives or when not to use it. Usage is inferred from the creation context.

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/kula-ai/kula-mcp-server'

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