Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company Insurance

update_company_insurance
Idempotent

Update a company insurance record in Procore by providing the company, insurance, and vendor IDs, and send only the fields to change; omitted fields retain their current values.

Instructions

Update the specified 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 id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified company 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, id, vendor_id. Procore API: Core > Directory. Endpoint: PATCH /rest/v1.0/companies/{company_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_idYesJSON request body field — 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?

The description reveals key behaviors beyond annotations: partial update semantics (omitted fields retain values), payload nesting handled by the tool, company_id default, the need to resolve id via a list tool, return value, and common error statuses (401/403/404). These enrich the agent's understanding beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true) without contradiction.

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 dense but well-organized. Each sentence serves a purpose: action, patch behavior, payload convenience, defaults, id prerequisite, return value, error handling, required parameters, and API location. No wasted words.

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?

Despite having 19 parameters and no output schema, the description covers all essential aspects: behavior, defaults, prerequisites, return value, error semantics, and endpoint. It is complete enough for an agent to invoke the tool correctly without additional documentation.

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%, so the baseline is 3. The description adds meaningful context: which parameters are required, how fields map from top-level arguments to the nested 'insurance' payload, and the default for company_id. It does not explain every field in detail, but the schema already covers that.

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 'Update the specified Insurance', identifying the verb (update) and the resource (Insurance). It further clarifies the company-level scope via company_id and the API endpoint, distinguishing it from siblings like create_company_insurance, delete_company_insurance, and update_project_insurance.

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 provides explicit guidance: 'Send only the fields you intend to change', 'resolve it with the matching list tool first', and notes that company_id defaults from procore_set_config. It does not explicitly name alternatives like update_project_insurance, but the company scope is clear from the endpoint and name.

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