Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Property Damage

update_property_damage
Idempotent

Update property damage record details: modify description, cost impact, affected company, or custom fields. Provide project ID and record ID; only included fields change.

Instructions

Updates the specified property damage record's attributes. All fields are optional. To clear a nullable field, explicitly pass null. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "property_damage" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified property damage on success. 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, id. Procore API: Project Management > Incidents. Endpoint: PATCH /rest/v1.0/projects/{project_id}/incidents/property_damages/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the property damage record. Use the `id` from the List or Create Property Damages response.
project_idYesURL path parameter — unique identifier for the project.
descriptionNoJSON request body field — description of event in Rich Text format
incident_idNoQuery string parameter — unique identifier of the incident
work_activity_idNoJSON request body field — the ID of the Work Activity
affected_company_idNoJSON request body field — the ID of the Affected Company
managed_equipment_idNoJSON request body field — the ID of the Managed Equipment
estimated_cost_impactNoJSON request body field — estimated cost impact of the record
responsible_company_idNoJSON request body field — the ID of the Responsible Company
custom_field_%{custom_field_definition_id}NoJSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ...
Behavior5/5

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

The description richly discloses behaviors beyond annotations: all fields optional, null clears nullable fields, omitted fields unchanged, fields nested under 'property_damage' in the payload, project_id defaults from procore_set_config, and error mapping (401/403/404). This is exactly the behavioral guidance an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence delivers useful information, logically ordered from core purpose to update semantics, payload handling, defaults, error handling, and endpoint context. There is no fluff, and the length is justified by the tool's complexity.

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

Completeness5/5

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

This update tool has 10 parameters, no output schema, and relies on annotations for safety. The description covers all essential aspects: partial-update semantics, null handling, payload nesting, id resolution, return value, common failures, required params, and API endpoint. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description adds crucial semantics: the payload nesting transformation, null-clearing behavior, default project_id, and id resolution via the list tool. These details go well beyond the schema's per-field 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 opens with 'Updates the specified property damage record's attributes,' using a specific verb and resource that clearly distinguishes it from create/destroy/show siblings. It is unambiguous about the tool's function.

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?

The description provides clear usage context: partial updates on existing records, 'resolve it with the matching list tool first' as a prerequisite, and project_id defaulting behavior. It does not explicitly name alternative tools like create/destroy, but the tool name and purpose make the usage evident.

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