Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Company Insurance

create_company_insurance

Create a new insurance record for a company in Procore by linking it to a vendor with company and vendor IDs.

Instructions

Create a new Insurance associated with the specified Company. 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: company_id, vendor_id. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/companies/{company_id}/insurances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
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
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that it returns the created object on success (HTTP 201), which is useful but minimal. No additional behavioral context like authentication needs or side effects. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is moderately concise but contains redundancy (mentions 'Directory records' twice). It front-loads the purpose but could be shortened by removing the repeated phrase. Not overly long, but not optimally structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 should cover what the created insurance object looks like. It only states 'returns the created object on success' without describing its structure or fields. This is a significant gap for a complex creation endpoint.

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 clear descriptions for all 18 parameters. The description highlights two required parameters (company_id, vendor_id) but adds no further semantic meaning beyond the schema. Baseline 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?

Clearly states 'Create a new Insurance associated with the specified Company' and identifies the API endpoint. However, it confusingly refers to 'Directory records' multiple times, which is not immediately relevant to insurance. Not explicitly distinguished from siblings like create_company_vendor_insurance, but the verb+resource is clear.

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?

Provides no guidance on when to use this tool versus alternatives like create_company_vendor_insurance or create_project_insurance. The statement 'Use this to create a new Directory records' does not clarify exclusion criteria or prerequisites beyond required parameters.

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