Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Checklist (Inspection) Schedules

list_checklist_inspection_schedules
Read-onlyIdempotent

Retrieve checklist inspection schedules for a project. Use to discover schedules or look up schedule IDs before calling tools that need them.

Instructions

Returns the Checklist Schedules from Checklists (Inspections) on the Project. Use this to discover checklist inspection schedules 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 checklist inspection schedules; 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: Project Management > Inspections. Endpoint: GET /rest/v1.0/projects/{project_id}/checklist/schedules

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — sort schedule(s) by the chosen param; check below for a list of options. The direction of sorting is ascending by default; for descending sort, insert the - symbol before the param.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
project_idYesURL path parameter — unique identifier for the project.
filters__endedNoQuery string parameter — return schedule(s) that are finished when true, returns unfinished schedule(s) otherwise
filters__ends_atNoQuery string parameter — return schedule(s) with the specified Last Inspection Due Date.
filters__frequencyNoQuery string parameter — return schedule(s) with the specified Frequency Types
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYY...
filters__assignee_idNoQuery string parameter — return schedule(s) with the specified Assignee IDs
filters__location_idNoQuery string parameter — return schedule(s) with the specified Location IDs
filters__equipment_idNoQuery string parameter — return schedule(s) with the specified Equipment IDs
filters__list_template_idNoQuery string parameter — return schedule(s) with the specified Inspection Template IDs
filters__inspection_type_idNoQuery string parameter — return schedule(s) with the specified Checklist Type IDs
filters__first_inspection_due_atNoQuery string parameter — return schedule(s) with the specified First Inspection Due Date
Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint, but the description adds meaningful behavioral context: pagination behavior (page/per_page, response reports pages remaining), error payload details (401/403/404), and the default behavior for project_id when omitted. This goes beyond the annotations without contradicting them.

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 moderately long but every sentence serves a purpose: purpose, use case, default, pagination, read-only nature, error handling, required parameters, and API reference. It is front-loaded with the main purpose and does not include unnecessary repetition.

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?

With 14 parameters and no output schema, the description covers return type (JSON array), pagination, common errors, default project_id behavior, and the API endpoint. It lacks a detailed breakdown of the schedule object structure, but that is not necessarily expected for a list tool.

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. The description adds value by mentioning that project_id defaults to the procore_set_config value when omitted (though schema lists it as required) and explaining that page/per_page control pagination. These details supplement the schema's parameter descriptions.

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 'Returns the Checklist Schedules from Checklists (Inspections) on the Project' with a specific verb and resource, distinguishing it from sibling tools like show_checklist_schedule. It also explains its role in discovering schedules and looking up IDs for use by other tools.

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 explicit usage guidance: 'Use this to discover checklist inspection schedules or to look up the id of one before calling a tool that needs it.' This clarifies when to use the tool, but it does not explicitly name alternatives or when not to use it, leaving a slight gap.

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