Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project Vendor Insurance

create_project_vendor_insurance

Creates a new insurance record for a project vendor in Procore. Use to add insurance details like policy number, effective date, and expiration date to a vendor's profile.

Instructions

Create a new Insurance associated with the specified Project Vendor. Use this to create a new Directory records in Procore. Creates a new Directory records and returns the created object on success (HTTP 201). Required parameters: project_id, vendor_id. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/projects/{project_id}/vendors/{vendor_id}/insurances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
vendor_idYesURL path parameter — unique identifier of the vendor
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
Behavior3/5

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

Annotations already indicate write, non-destructive, non-idempotent, open world. The description adds that it returns HTTP 201 but does not elaborate on side effects, permissions, or other behaviors beyond the annotations.

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 concise at 4 sentences, but contains slight redundancy (mentions 'Directory records' twice). It front-loads the main action and includes API details, making it reasonably structured.

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?

Given 18 parameters and no output schema, the description adequately explains the tool's purpose and endpoint. It mentions project and vendor context, which helps distinguish from company-level insurance tools. However, it could better clarify the hierarchical context.

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 detailed descriptions for each parameter. The description itself only highlights required parameters and does not add new information, so baseline of 3 is appropriate.

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?

The description clearly states it creates an insurance record for a project vendor, and specifies the endpoint and required parameters. However, the phrasing 'Directory records' is slightly awkward and it does not explicitly differentiate from similar sibling tools like create_company_vendor_insurance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only says to use this tool to create insurance records, but provides no guidance on when not to use it or alternatives. Given many sibling tools for similar purposes, explicit usage context is missing.

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