Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Calendar Item

update_calendar_item

Update attributes of an existing Schedule (Legacy) calendar item. Modifies only the supplied fields and returns the updated object.

Instructions

Update attributes on a single Calendar Item. Use this to update an existing Schedule (Legacy) records (only the supplied fields are changed). Updates the specified Schedule (Legacy) records and returns the modified object on success. Required parameters: project_id, id. Procore API: Project Management > Schedule (Legacy). Endpoint: PATCH /rest/v1.0/projects/{project_id}/schedule/calendar_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Schedule (Legacy) resource
assigned_idNoJSON request body field — iD of the assigned user for the Calendar Item
colorNoJSON request body field — calendar Item color (as a hex triplet)
descriptionNoJSON request body field — calendar Item description
finishNoJSON request body field — the finish date of the Calendar Item
nameNoJSON request body field — calendar Item name
percentageNoJSON request body field — calendar Item completion percentage
privateNoJSON request body field — calendar Item private status
startNoJSON request body field — the start date of the Calendar Item
Behavior3/5

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

Annotations already declare readOnlyHint=false, so the mutation behavior is clear. The description adds that it returns the modified object, but no further behavioral details (auth, rate limits).

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 three sentences, covering purpose, partial update behavior, and return value. The API endpoint info is slightly extraneous but not harmful.

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?

Given 10 parameters with full schema coverage and no output schema, the description adequately covers the core behavior and constraints (partial update, required params).

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 detailed descriptions for each parameter. The description only reiterates required parameters, adding no additional semantic value beyond the schema.

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 updates a single Calendar Item (Schedule Legacy record), distinguishing it from other update tools in the sibling list by specifying the resource type.

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 indicates when to use (update existing records) and mentions partial updates, but does not provide explicit alternatives or when-not-to-use guidance.

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