Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Environmental

update_environmental

Update an existing environmental incident record by providing project ID and incident ID. Modify details such as description, cost impact, quantity, or custom fields to keep records accurate.

Instructions

Updates the Environmental record. Use this to update an existing Incidents (only the supplied fields are changed). Updates the specified Incidents and returns the modified object on success. Required parameters: project_id, id. Procore API: Project Management > Incidents. Endpoint: PATCH /rest/v1.0/projects/{project_id}/incidents/environmentals/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Incidents resource
incident_idNoQuery string parameter — unique identifier of the incident
environmental_type_idNoJSON request body field — the ID of the Environmental Type
descriptionNoJSON request body field — description of event in Rich Text format
estimated_cost_impactNoJSON request body field — estimated cost impact of the record
quantity_valueNoJSON request body field — numeric portion of the "quantity" field
quantity_unit_of_measureNoJSON request body field — unit of measure for the "quantity" field (19 possible values)
affected_company_idNoJSON request body field — the ID of the Affected Company
managed_equipment_idNoJSON request body field — the ID of the Managed Equipment
work_activity_idNoJSON request body field — the ID of the Work Activity
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 ...
Behavior3/5

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

Annotations already indicate the tool is not read-only and not destructive. The description adds context that the update is partial (only supplied fields change) and returns the modified object, but lacks details on permissions or side effects.

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 (three sentences) and front-loaded with the core purpose. It efficiently includes technical details without unnecessary verbosity.

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 12 parameters and no output schema, the description provides basic context (patch behavior, endpoint) but lacks explanation of what an Environmental record is and common usage patterns, leaving some gaps.

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?

Input schema covers 100% of parameters with clear descriptions. The description redundantly lists required parameters but adds no significant meaning beyond the schema, resulting in a baseline score of 3.

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 updates an Environmental record and returns the modified object. However, it inconsistently refers to 'Incidents' instead of 'Environmental,' which may cause minor confusion.

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 this tool should be used to update existing records and mentions that only supplied fields are changed. No explicit guidance on when not to use it or comparison with sibling update tools is provided.

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