Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company Vendor Insurance

update_company_vendor_insurance
Idempotent

Update a vendor's insurance record for a company by sending only the fields to change. Specify company, vendor, and insurance ID; omitted fields remain unchanged.

Instructions

Update the specified Company 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. company_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 company 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: 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
idYesURL path parameter — unique identifier of the Directory resource
nameNoJSON request body field — provider name
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
company_idYesURL path parameter — unique identifier for the company.
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
Behavior5/5

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

Beyond the annotations (write, non-destructive, idempotent), the description discloses partial-update behavior, payload nesting under 'insurance', the company_id default, success return value, and error payloads with common HTTP statuses. This context helps the agent understand side effects and failure modes, adding real value over the structured metadata.

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 a single dense paragraph but every sentence earns its place: purpose, usage, defaults, resolution prerequisite, return, and errors. It is longer than the ideal two-sentence description but appropriately sized for a 19-parameter update operation.

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?

The description is complete for an update tool: it states what it does, how to call it, what is required, what to do before calling (resolve IDs), what it returns, and how failures manifest. With no output schema, it still tells the agent what to expect on success and failure.

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 provides 100% field coverage and names each parameter. The description adds value by explaining that only changed fields should be sent, that top-level arguments are nested under 'insurance' in the payload, and that company_id defaults to the configured value when omitted – details not in the schema.

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 a specific verb and resource: 'Update the specified Company Vendor Insurance.' This clearly differentiates it from sibling tools like list_company_vendor_insurances, create_company_vendor_insurance, and delete_company_vendor_insurance. The endpoint PATCH /rest/v1.0/companies/{company_id}/vendors/{vendor_id}/insurances/{id} further confirms the update semantics.

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 gives clear usage guidance: partial update semantics ('Send only the fields you intend to change'), the company_id default from procore_set_config, and the prerequisite to resolve vendor_id and id with the matching list tool. It also warns about failure scenarios (401/403/404). It does not explicitly list alternative tools to avoid, but the context is clear.

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