Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project Vendor Insurance

create_project_vendor_insurance

Create a new insurance record for a specific project vendor by providing project and vendor IDs. Returns the created insurance with its new ID, enabling easy tracking of vendor insurance compliance.

Instructions

Create a new Insurance associated with the specified Project Vendor. Pass the record's fields as top-level arguments — they are nested under "insurance" in the request payload for you. project_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 project 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: 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
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
project_idYesURL path parameter — unique identifier for the project.
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 (readOnlyHint false, idempotentHint false), the description adds substantial behavioral detail: payload nesting ('nested under "insurance" in the request payload for you'), config-based defaulting, non-idempotency, HTTP 201 response, and common failure statuses. These are concrete behaviors the agent would not know otherwise.

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 long but every sentence carries unique information: purpose, payload transformation, defaults, vendor resolution, return behavior, error handling, required parameters, and API location. No filler or redundancy. The structure is logical and front-loaded with the core purpose.

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 18 parameters, no output schema, and the presence of annotations, the description covers all essential aspects for selection and invocation: what it does, how parameters map, required vs defaulted fields, return value, error codes, and the exact API endpoint. The absence of output schema is mitigated by stating the tool returns the created record with its id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds critical meaning: top-level arguments are wrapped under 'insurance' in the request payload, project_id has a default from config despite being listed as required, and vendor_id must identify an existing parent record. These clarify how to invoke the tool beyond the raw 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 clearly states the tool's action: 'Create a new Insurance associated with the specified Project Vendor.' The verb 'Create' and resource 'Project Vendor Insurance' are specific, and the association with a vendor distinguishes it from general project insurance tools like create_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?

Provides clear usage context: vendor_id must reference an existing parent record and should be resolved with a list tool first; project_id defaults to the procore_set_config value when omitted. It does not explicitly mention alternatives (e.g., update vs create) but the purpose is clear enough that this is implied. Non-idempotency is noted with 'calling it again creates another record.'

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