Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A Resource Request On A Project

create_a_resource_request_on_a_project

Create a resource request for a project to allocate resources by work hours or percent allocation. Specify start and end dates.

Instructions

Creates a new Resource Request for a specified project within a given company. Resource requests can be based on work hours (start_time and end_time) or percent allocation (percent_allocated). 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, project_id, start_day, end_day. Procore API: Resource Management > Resource Planning. Endpoint: POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/projects/{project_id}/resource-requests

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...
project_idYesURL path parameter — unique identifier for the project
start_dayYesJSON request body field — the first day the requested resource is needed (ISO 8601).
end_dayYesJSON request body field — the last day the requested resource is needed (ISO 8601).
start_timeNoJSON request body field — start time of the request (HH:MM am/pm format).
end_timeNoJSON request body field — end time of the request (HH:MM am/pm format).
percent_allocatedNoJSON request body field — allocation percentage if the request is not hour-based.
quantityNoJSON request body field — number of resource requests to create.
job_title_idNoJSON request body field — job Title UUID for this request.
category_idNoJSON request body field — uUID of the Project Category.
subcategory_idNoJSON request body field — uUID of the Project Subcategory.
state_idNoJSON request body field — uUID of the Assignment State.
work_scope_textNoJSON request body field — scope of Work for the Resource Request.
instruction_textNoJSON request body field — instructions for the Resource Request.
tag_idsNoJSON request body field — array of UUIDs representing Tags.
work_daysNoJSON request body field — object to control working days (Sunday - Saturday as 0-6 index).
Behavior3/5

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

Annotations already indicate non-read-only, non-destructive, non-idempotent behavior. The description adds that the tool creates a record and returns HTTP 201, but does not disclose permissions, rate limits, or side effects beyond that.

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 relatively concise and front-loaded, but contains redundancy (e.g., 'Creates a new Resource Planning records' repeated). It efficiently conveys the core purpose, required parameters, and API endpoint.

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 16 parameters and no output schema, the description covers required params but fails to explain the mutually exclusive relationship between hour-based and percent-based parameters, nor does it describe the return object structure or nested objects work_days/tag_ids.

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

Parameters4/5

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

With 100% schema coverage, the baseline is 3. The description adds value by explaining the two modes (work hours vs. percent allocation), clarifying the relationship between parameters. However, it does not detail nested objects (work_days) or array parameters (tag_ids).

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 Resource Request for a specified project, differentiating it from sibling creation tools for other objects. It specifies the resource type, scope (company and project), and required parameters.

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?

The description lacks explicit when-to-use or when-not-to-use guidance compared to alternatives. While it states 'Use this to create new Resource Planning records,' it does not contrast with other creation tools or provide exclusion criteria.

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