Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Time Off For A Person

create_time_off_for_a_person

Create a new time off entry for a person in Procore by specifying company, person, and date range. Returns the created record.

Instructions

Creates a new Time Off entry for a specified Person within a given company. Use this to create a new Resource Planning records in Procore. Creates a new Resource Planning records and returns the created object on success (HTTP 201). Required parameters: company_id, person_id, start_day, end_day. Procore API: Resource Management > Resource Planning. Endpoint: POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/people/{person_id}/time-off

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company. This parameter accepts both formats: - **Recommended**: Procore company ID (integer) - Use this for new integrations - Legacy: LaborChart UUID format (uuid string...
person_idYesURL path parameter — unique identifier for the person
start_dayYesJSON request body field — the start date of the time off.
end_dayYesJSON request body field — the end date of the time off.
apply_to_saturdayNoJSON request body field — whether the time off applies to Saturdays.
apply_to_sundayNoJSON request body field — whether the time off applies to Sundays.
is_paidNoJSON request body field — whether the time off is paid.
reasonNoJSON request body field — the reason for the time off.
repeatNoJSON request body field — repeat interval of the time off instances.
batch_start_timeNoJSON request body field — start time of the time off (HH:MM am/pm).
batch_end_timeNoJSON request body field — end time of the time off (HH:MM am/pm).
cadenceNoJSON request body field — cadence of the repeating time off.
repeat_end_dayNoJSON request body field — the end date of the repeating time off.
Behavior4/5

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that it returns the created object on HTTP 201, providing useful behavioral context beyond annotations.

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 concise with 4 sentences, front-loading the main purpose. Minor redundancy (repeats 'Creates a new Resource Planning records') but overall efficient.

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?

Given 13 parameters and no output schema, the description explains the main purpose, required params, and return value (HTTP 201). It does not detail response structure or optional parameters, but schema covers those. Adequate but not thorough.

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 baseline is 3. The description mentions required parameters but does not add meaning beyond what the schema already provides (e.g., formats or constraints).

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 it creates a new Time Off entry for a specified person within a company, using specific verbs and resources. It distinguishes from siblings like 'create_a_person' or 'delete_a_time_off_record' by focusing on time off entries.

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 explicitly states when to use the tool ('to create a new Resource Planning records') and lists required parameters, but does not provide when-not or alternatives. Usage context is clear.

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/TylerIlunga/procore-mcp-server'

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