Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_checklist_inspection_schedules

Retrieve scheduled inspection checklists for a Procore project, enabling project managers to track and filter upcoming inspections by type, frequency, location, and due dates.

Instructions

List Checklist (Inspection) Schedules. [Project Management/Inspections] GET /rest/v1.0/projects/{project_id}/checklist/schedules

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
filters__updated_atNoReturn 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__inspection_type_idNoReturn schedule(s) with the specified Checklist Type IDs
filters__frequencyNoReturn schedule(s) with the specified Frequency Types
filters__location_idNoReturn schedule(s) with the specified Location IDs
filters__list_template_idNoReturn schedule(s) with the specified Inspection Template IDs
filters__assignee_idNoReturn schedule(s) with the specified Assignee IDs
filters__first_inspection_due_atNoReturn schedule(s) with the specified First Inspection Due Date
filters__ends_atNoReturn schedule(s) with the specified Last Inspection Due Date.
filters__endedNoReturn schedule(s) that are finished when true, returns unfinished schedule(s) otherwise
filters__equipment_idNoReturn schedule(s) with the specified Equipment IDs
sortNoSort 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.
pageNoPage
per_pageNoElements per page
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'List' and includes a GET endpoint, implying a read-only, non-destructive operation, but doesn't explicitly confirm safety, rate limits, authentication needs, or pagination behavior. The description lacks details on what 'List' entails (e.g., returns an array, may be paginated). While the endpoint hints at a RESTful read, more explicit behavioral traits would improve transparency.

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 and front-loaded with the core purpose: 'List Checklist (Inspection) Schedules.' The additional context '[Project Management/Inspections] GET /rest/v1.0/projects/{project_id}/checklist/schedules' is relevant for API integration but could be more streamlined. It avoids unnecessary verbosity, and every part (purpose, context, endpoint) earns its place, though the endpoint detail might be better suited for structured fields.

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 complexity (14 parameters, no annotations, no output schema), the description is minimally adequate. It states the purpose and endpoint but lacks details on output format, error handling, or behavioral constraints. The schema covers inputs thoroughly, but without annotations or output schema, the description should ideally add more context about what the list returns (e.g., array of schedule objects) and any usage limits. It's complete enough for a basic read operation but leaves gaps for a tool with many filter options.

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 the schema fully documents all 14 parameters, including their types, descriptions, and constraints (e.g., required project_id, filter arrays, sort enum). The description adds no parameter-specific information beyond implying listing with filters via the endpoint context. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'List Checklist (Inspection) Schedules.' It specifies the resource (checklist inspection schedules) and includes the context '[Project Management/Inspections]' and endpoint 'GET /rest/v1.0/projects/{project_id}/checklist/schedules', which clarifies it's a read operation. However, it doesn't explicitly differentiate from sibling tools like 'list_checklist_schedule_attachments' or 'list_checklist_inspections', though the name and endpoint suggest it's for schedules rather than individual inspections or attachments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions the project context and endpoint but doesn't specify prerequisites, such as needing a valid project_id, or compare it to other listing tools (e.g., for filtering vs. unfiltered lists). Without explicit when/when-not instructions or named alternatives, the agent must infer usage from the schema and context alone.

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