Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company Vendor Insurance

update_company_vendor_insurance

Update a vendor's insurance details for a Procore company by specifying company ID, vendor ID, and insurance ID. Change policy number, expiration date, status, and more.

Instructions

Update the specified Company 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: company_id, vendor_id, id. Procore API: Core > Directory. Endpoint: PATCH /rest/v1.0/companies/{company_id}/vendors/{vendor_id}/insurances/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
vendor_idYesURL path parameter — unique identifier of the vendor
idYesURL path parameter — unique identifier of the Directory resource
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
Behavior4/5

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

The description states 'only the supplied fields are changed', indicating partial update behavior, which is not disclosed by annotations. Annotations already show readOnlyHint=false and destructiveHint=false, so the description adds value by clarifying the update is not destructive and is a patch operation.

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?

The description is three concise sentences: purpose, behavior, and required fields/API reference. No extraneous information, and it is front-loaded with the action.

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

Completeness4/5

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

For a tool with 19 parameters and no output schema, the description covers the key aspects: partial update, return of modified object, and required identifiers. It could provide more context on the 'Directory records' concept but is sufficient for an AI agent to understand the tool's purpose.

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%, so the schema already documents all parameters. The description only repeats the required parameters (company_id, vendor_id, id) and does not add further semantic meaning or usage context for any parameter.

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 clearly states the action: 'Update the specified Company Vendor Insurance', which is a specific verb+resource combination. It distinguishes from sibling tools like create and delete by explicitly saying 'update an existing Directory records'.

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 says 'Use this to update an existing Directory records', which implies it is for modifications, not creation. However, it does not explicitly mention when to use alternatives like create_company_vendor_insurance, so it loses a point.

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