Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project Vendor Insurance

update_project_vendor_insurance
Idempotent

Update vendor insurance details within a project. Send only the fields to change; omitted fields keep their existing values.

Instructions

Update the specified Project Vendor Insurance. 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 "insurance" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and vendor_id, id must identify existing parent records — resolve them with the matching list tool first. Returns the modified project vendor insurance 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, 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
idYesURL path parameter — unique identifier of the Directory resource
nameNoJSON request body field — provider name
viewNoQuery string parameter — extended view of data
limitNoJSON request body field — the limit for this Directory operation
notesNoJSON request body field — the notes for this Directory operation
exemptNoJSON request body field — exempt status
statusNoJSON request body field — the status for this Directory operation
origin_idNoJSON request body field — unique identifier of the origin
vendor_idYesURL path parameter — unique identifier of the vendor
project_idYesURL path parameter — unique identifier for the project.
origin_dataNoJSON request body field — the origin data for this Directory operation
info_receivedNoJSON request body field — information received (or not)
policy_numberNoJSON request body field — the policy number for this Directory operation
effective_dateNoJSON request body field — the effective date in YYYY-MM-DD format
insurance_setsNoJSON request body field — the insurance sets for this Directory operation
insurance_typeNoJSON request body field — the insurance type for this Directory operation
expiration_dateNoJSON request body field — the expiration date in YYYY-MM-DD format
division_templateNoJSON request body field — the division template for this Directory operation
additional_insuredNoJSON request body field — additional Individuals and/or Companies Insured
enable_expired_insurance_notificationsNoJSON request body field — enable/Disable expired insurance notifications
Behavior4/5

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

Annotations already mark this as a non-read-only, idempotent, non-destructive operation. The description adds valuable behavioral context: partial update semantics, automatic nesting under 'insurance' in the payload, project_id falling back to procore_set_config, and detailed error response patterns (401, 403, 404). This goes beyond the annotations to clarify how the tool behaves in practice.

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 dense but every sentence serves a purpose: action, partial update behavior, payload mapping, ID prerequisites, defaults, return value, error handling, and API reference. It is front-loaded with the main verb+resource. While longer than the calibration high example, the length is justified by the tool's complexity (20 parameters) and the critical semantic details it conveys.

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?

Given there is no output schema, the description compensates by explicitly stating 'Returns the modified project vendor insurance on success' and detailing error payloads. It also covers required parameters, the default for project_id, and prerequisites for vendor_id/id. This is fully complete for a mutation tool of this complexity.

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

Parameters4/5

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

Schema coverage is 100%, with each parameter described. The description adds meaning beyond the schema by clarifying that fields are nested under 'insurance' despite being passed as top-level arguments, and that project_id has a default from procore_set_config. This explains the relationship between the tool's interface and the underlying API payload.

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 'Update the specified Project Vendor Insurance' which is a specific verb+resource. It clearly distinguishes from sibling tools like update_project_insurance or update_company_vendor_insurance by explicitly naming 'Project Vendor Insurance' and including the exact endpoint. No ambiguity about what this tool does.

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?

Provides clear guidance: partial update behavior ('Send only the fields you intend to change'), ID resolution prerequisite ('resolve them with the matching list tool first'), and project_id default behavior. It doesn't explicitly name alternative tools for contrast, but the context of when to use this tool is well established through resource specificity and required parameters.

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