Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company Insurance

update_company_insurance

Update an existing insurance record in the Procore company directory. Modify fields like effective date, expiration, status, and policy details.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
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
vendor_idYesJSON request body field — unique identifier of the vendor
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?

Description discloses that only supplied fields are changed (partial update), returns the modified object on success, and lists required parameters. Annotations (readOnlyHint=false) agree with the update behavior. No contradictions. It adds value beyond annotations by specifying the PATCH method and partial update nature.

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?

Description is three sentences, each serving a distinct purpose: action statement, update behavior, and required parameters with API reference. No extraneous information. Front-loaded with the core purpose.

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 the complexity (19 parameters, no output schema), the description covers the essential purpose and behavior but does not explain return values, error handling, or permission requirements. It lists required params but offers no guidance on optional fields or usage patterns. Adequate but not thorough.

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% with descriptions for all 19 parameters. Description highlights three required parameters (company_id, id, vendor_id) but does not add further semantic meaning to individual parameters. Baseline score of 3 is appropriate as schema already covers descriptions.

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?

Description clearly states 'Update the specified Insurance' and mentions partial update behavior. The name and title align with updating a company insurance record. However, it does not explicitly distinguish from sibling update tools like update_project_insurance, though the context of company vs project is implied.

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 instruction 'Use this to update an existing Directory records (only the supplied fields are changed)' provides basic usage context. It does not mention when not to use this tool or suggest alternative tools like create or delete insurance. No exclusions or limitations are stated.

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