Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Company Insurance

create_company_insurance

Create a new insurance record for a specified company and vendor, returning the newly created insurance ID.

Instructions

Create a new Insurance associated with the specified Company. 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. Creates the company 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}/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_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 goes well beyond the annotations by explaining that the tool is non-idempotent ('calling it again creates another record'), how errors surface (HTTP status payload, common 401/403/404), and the return behavior (new id, HTTP 201). This provides valuable operational context that annotations alone don't convey.

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 well-structured, leading with the primary purpose, then payload handling, defaults, behavior, errors, and endpoint. Every sentence adds useful information, and the length is justified for a tool with 18 parameters.

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?

For a complex creation tool with no output schema, the description covers all essential dimensions: purpose, payload mapping, defaults, idempotency, error handling, required parameters, and the exact API endpoint. It is sufficiently complete for an agent to invoke it 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?

With 100% schema coverage, the baseline is 3, but the description adds meaningful context: fields should be passed as top-level arguments (not nested under 'insurance'), company_id defaults to the configured value, and company_id/vendor_id are required. This helps the agent correctly structure the call beyond what the schema states.

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 opens with a specific verb and resource ('Create a new Insurance associated with the specified Company'), clearly distinguishing this from sibling tools like update/delete/list company insurance. It also highlights the non-idempotent creation behavior, reinforcing its create-only purpose.

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 clear context for when to use it: creating a new insurance, with the note that calling again creates another record. It also gives operational guidance (company_id default, required parameters, error status codes). However, it does not explicitly mention alternative tools for update/delete/list, so it falls short of explicitly naming exclusions.

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