Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project Vendor Insurance

update_project_vendor_insurance

Update a vendor's insurance record for a specific project by providing the project ID, vendor ID, and insurance ID. Modify only the fields you need, such as effective date, expiration date, or status.

Instructions

Update the specified Project Vendor Insurance. Use this to update an existing Directory records (only the supplied fields are changed). Updates the specified Directory records and returns the modified object on success. Required parameters: project_id, vendor_id, id. Procore API: Core > Directory. Endpoint: PATCH /rest/v1.0/projects/{project_id}/vendors/{vendor_id}/insurances/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
vendor_idYesURL path parameter — unique identifier of the vendor
idYesURL path parameter — unique identifier of the Directory resource
viewNoQuery string parameter — extended view of data
effective_dateNoJSON request body field — the effective date in YYYY-MM-DD format
enable_expired_insurance_notificationsNoJSON request body field — enable/Disable expired insurance notifications
exemptNoJSON request body field — exempt status
expiration_dateNoJSON request body field — the expiration date in YYYY-MM-DD format
info_receivedNoJSON request body field — information received (or not)
insurance_typeNoJSON request body field — the insurance type for this Directory operation
limitNoJSON request body field — the limit for this Directory operation
nameNoJSON request body field — provider name
notesNoJSON request body field — the notes for this Directory operation
policy_numberNoJSON request body field — the policy number for this Directory operation
statusNoJSON request body field — the status for this Directory operation
additional_insuredNoJSON request body field — additional Individuals and/or Companies Insured
division_templateNoJSON request body field — the division template for this Directory operation
insurance_setsNoJSON request body field — the insurance sets for this Directory operation
origin_dataNoJSON request body field — the origin data for this Directory operation
origin_idNoJSON request body field — unique identifier of the origin
Behavior3/5

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

Annotations already indicate a mutation (readOnlyHint=false). The description adds that it returns the modified object on success and that only supplied fields change. It does not contradict annotations. No additional behavioral traits like side effects or authentication needs are disclosed, but annotations cover the safety profile.

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, with three sentences covering purpose, partial update behavior, required parameters, and API reference. It is front-loaded and avoids unnecessary filler.

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 exists, but the description mentions 'returns the modified object on success'. With 20 parameters fully described in the schema, the description provides adequate context for basic use, though it could mention format constraints or conditional fields.

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?

The input schema has 100% coverage with descriptions for all parameters. The description only reiterates the required parameters (project_id, vendor_id, id) already marked as required in the schema, adding no extra 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 description clearly states the tool updates a Project Vendor Insurance with a specific verb ('Update') and resource. It mentions updating existing Directory records and required parameters. However, it does not explicitly differentiate this tool from siblings like update_company_vendor_insurance or update_project_vendor, though the name provides context.

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 says 'only the supplied fields are changed', indicating a partial update behavior. It lists required parameters. But it does not specify when to use this tool versus alternatives like create_project_vendor_insurance, nor does it provide exclusion criteria or prerequisites.

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