Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Company Vendor Insurance

create_company_vendor_insurance

Create a new insurance record for a Procore company vendor using company and vendor IDs, with optional policy details, and get the new record's ID.

Instructions

Create a new Insurance associated with the specified Company Vendor. 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 must identify an existing parent record — resolve it with the matching list tool first. Creates the company vendor insurance and returns it with its new id (HTTP 201); calling it again creates another record. 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. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/companies/{company_id}/vendors/{vendor_id}/insurances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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?

Adds significant behavioral details beyond annotations: fields are nested under 'insurance' in the payload, calling again creates another record (non-idempotent), returns the new id with HTTP 201, and describes common error statuses (401, 403, 404). This complements the idempotentHint=false annotation and provides transparent failure modes.

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 every sentence adds value: purpose, payload handling, parameter defaults, idempotency, error handling, and endpoint. It is front-loaded with the core action and structured logically, with no fluff.

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 the tool's complexity (18 params, no output schema), the description covers the essential operational context: required parameters, parent record resolution, payload nesting, return behavior, and error scenarios. It is complete enough for an agent to invoke correctly.

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 baseline is 3. The description adds meaning for company_id (defaults from config), vendor_id (must be an existing parent record resolved via list tool), and the general payload nesting instruction, exceeding baseline and compensating for any ambiguity in the generic schema descriptions.

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 states a specific action: 'Create a new Insurance associated with the specified Company Vendor.' This clearly distinguishes it from sibling tools like list, update, delete, and sync company vendor insurance by specifying a create operation on a company vendor resource.

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 context: vendor_id must be resolved with a list tool first, and company_id defaults to the procore_set_config value. However, it does not explicitly name alternatives for when not to use (e.g., using update for existing records), so it falls short of explicit when/when-not guidance.

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