Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Lookaheads

list_lookaheads
Read-onlyIdempotent

Retrieve all lookaheads for a project to discover schedule lookaheads or fetch a lookahead ID for use in other Procore tools. Requires project_id; read-only.

Instructions

Returns all Lookaheads for the project. Use this to discover lookaheads or to look up the id of one before calling a tool that needs it. project_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of lookaheads; page and per_page control pagination and the response reports how many pages remain. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id. Procore API (v1.1): Project Management > Schedule (Legacy). Endpoint: GET /rest/v1.1/projects/{project_id}/schedule/lookaheads

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for paginated results (default: 1, 1-indexed)
per_pageNoNumber of items per page (default: 100, max: 100)
project_idYesURL path parameter — unique identifier for the project.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, but the description adds meaningful behavior beyond that: pagination mechanics ('response reports how many pages remain'), error payload structure with common HTTP statuses (401/403/404), and default project_id behavior. No contradiction with annotations.

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?

Every sentence earns its place: purpose, use case, defaults, pagination, read-only emphasis, error reporting, required params, and API endpoint. Dense but not bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-param tool with no output schema, the description covers return format, pagination, error behavior, default parameter handling, and API context. No major gaps that would hinder an agent from invoking or interpreting results.

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?

Schema coverage is 100%, so baseline is 3. Description adds value by noting project_id defaults to the procore_set_config value when omitted, which is beyond the schema. Pagination params are briefly referenced but largely repeat schema semantics.

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?

States the specific verb+resource+scope: 'Returns all Lookaheads for the project.' Clearly distinguishes from sibling tools like show_lookahead by emphasizing the plural/all and the use case of discovering lookaheads or looking up IDs before other calls.

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?

Provides clear context: 'Use this to discover lookaheads or to look up the id of one before calling a tool that needs it.' Also mentions the project_id default from procore_set_config. Does not explicitly name an alternative for fetching a single lookahead, so not a full 5.

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