Skip to main content
Glama
TylerIlunga

Procore MCP Server

Calculate When The First Inspection Of An Inspection Schedule Will Be Created

calculate_when_the_first_inspection_of_an_inspection_schedule
Read-onlyIdempotent

Calculates the creation date for the first inspection in a schedule, using start/end dates, frequency, and days before due date.

Instructions

Calculates the creation date for the first Inspection to be created based on an Inspection Schedule's temporal attributes. Use this to read information about Inspections from Procore. Returns a paginated JSON array of Inspections. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id, starts_at, ends_at, frequency, days_created_before_due_date. Procore API: Project Management > Inspections. Endpoint: GET /rest/v1.0/projects/{project_id}/checklist/schedules/calculate_first_inspection_created_at

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
starts_atYesJSON request body field — schedule start date
ends_atYesJSON request body field — schedule end date. When frequency is 'once' this should be the same value as starts_at.
frequencyYesJSON request body field — schedule frequency type name
days_created_before_due_dateYesJSON request body field — number of days before the inspection due date that the inspection should be created
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior2/5

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

Annotations provide readOnlyHint=true, but the description adds confusion by stating both a calculation and a paginated array return. The behavioral trait of returning a list vs. a single date is unclear. No additional behavioral context beyond annotations.

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 moderately concise at four sentences, but includes contradictory information (calculation vs. paginated array). Front-loading is adequate, but the conflicting content reduces overall conciseness.

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

Completeness2/5

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

No output schema is provided, and the description does not clarify the exact return structure. The statement 'Returns a paginated JSON array of Inspections' conflicts with the tool's purpose of calculating a single date. Important context about what is actually returned is missing.

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% with clear descriptions for each parameter. The description lists required parameters but does not add significant new semantics beyond what the schema provides. Baseline score of 3 is appropriate.

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

Purpose3/5

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

The description states it calculates the creation date for the first inspection, but then contradicts itself by saying it returns a paginated JSON array of Inspections. This inconsistency undermines clarity. The verb 'calculates' is specific, but the purpose is muddled by the mention of paginated results.

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?

No guidance on when to use this tool versus the sibling 'calculate_number_of_inspections_to_create_based_on_schedule'. The description only lists required parameters, which is not usage guidance. Context for alternatives is absent.

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