Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Restore Change Event

restore_change_event
Idempotent

Restore a previously deleted change event in Procore. Provide the change event ID and project ID to reinstate it.

Instructions

Restores a Previously Deleted Change Event. Use this to update an existing Change Events (only the supplied fields are changed). Updates the specified Change Events and returns the modified object on success. Required parameters: id, project_id. Procore API (v1.1): Construction Financials > Change Events. Endpoint: PUT /rest/v1.1/change_events/{id}/restore

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Change Events resource
project_idYesQuery string parameter — unique identifier for the project.

Tool Definition Quality

B3.1/5.0
Behavior3/5

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

Annotations already indicate non-read-only, non-destructive, and idempotent. The description adds that it returns the modified object but 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?

Four sentences with some redundancy (e.g., 'Required parameters' repeated from schema). Could be more concise without the endpoint and API version details.

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?

No output schema, but description states 'returns the modified object.' Lacks error conditions or behavior when restoring non-deleted events. Adequate for a simple tool.

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 descriptions for both parameters. The description merely restates required parameters, adding no new meaning beyond the schema.

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 title and first sentence clearly state 'Restores a Previously Deleted Change Event.' However, the second sentence says 'Use this to update existing Change Events,' which conflates restore with update, causing slight confusion.

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 restore vs. other tools like update_change_event or delete. The description does not specify prerequisites or alternatives.

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