Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Look Ahead Data

get_look_ahead_data
Read-onlyIdempotent

Retrieve future assignments and availability details for people in a group. Filter by job titles, project numbers, or employee numbers to get customized workforce planning data.

Instructions

Fetches the Look Ahead report which provides future assignments and availability details for People within a specified Group. To span all Groups in the company, use "all" in place of {group_id}. Use this to fetch the full details of a specific Resource Planning records by its identifier. Returns a JSON object describing the requested Resource Planning records. Required parameters: company_id, group_id. Procore API: Resource Management > Resource Planning. Endpoint: GET /rest/v1.0/workforce-planning/v2/companies/{company_id}/groups/{group_id}/reports/look-ahead

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...
group_idYesURL path parameter — unique identifier for the group
jobTitleIdsNoQuery string parameter — an array of UUIDs representing the Job Titles to include in the report. People with Job Titles not in this list will be excluded.
assignmentCountNoQuery string parameter — the number of future assignments to return per person.
projectNameNoQuery string parameter — whether to include the project name for each assignment.
project_numberNoQuery string parameter — filters items by their exact project number. The query performs an exact match. Example usage: `/v2/companies/{company_id}/...?project_number=BR-2024`
assignmentStartNoQuery string parameter — whether to include the assignment start date.
assignmentEndNoQuery string parameter — whether to include the assignment end date.
availableAfterDateNoQuery string parameter — whether to include the last day a person is assigned in the future.
employee_numberNoQuery string parameter — filter results by the exact employee number of the Person.
jobTitleNoQuery string parameter — whether to include the person's Job Title.
assignmentDurationNoQuery string parameter — whether to include a calculated duration for each assignment.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive behavior. The description adds context about the specific endpoint and required parameters, but does not elaborate on return structure or pagination. This is sufficient given the annotation coverage.

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

Conciseness3/5

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

The description is somewhat verbose with redundant phrases like 'Use this to fetch the full details of a specific Resource Planning records by its identifier' which is vague. It could be more concise and front-loaded.

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 the 14 parameters and no output schema, the description could provide more details about the report structure or examples. It covers the basics but lacks completeness for a complex tool.

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 coverage is 100%, so all parameters have descriptions. The description only restates required parameters (company_id, group_id) without adding new meaning. Baseline score of 3 is appropriate.

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 the tool fetches the Look Ahead report for future assignments and availability within a group. It explains the special 'all' parameter for covering all groups, and the endpoint context distinguishes it from related tools that list people or assignments individually.

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 mentions using 'all' for spanning groups but does not explicitly state when to choose this tool over siblings like get_all_people_belonging_to_a_group or get_person_assignments. It lacks when-not-to-use guidance or clear alternatives.

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