Skip to main content
Glama
TylerIlunga

Procore MCP Server

create_project_vendor

Add a vendor to a Procore project by providing details like name, contact information, and project-specific attributes to manage construction suppliers.

Instructions

Create project vendor. [Core/Directory] POST /rest/v1.0/projects/{project_id}/vendors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
viewNoThe normal view provides what is shown below. The extended view is the same as the normal view but includes children_count, legal_name, parent, and bidding. The default view is normal.
run_configurable_validationsNoIf true, validations are run for the corresponding Configurable Field Set.
abbreviated_nameNoAbbreviated name
addressNoStreet address
authorized_bidderNoAuthorized bidder status
business_phoneNoBusiness phone number
cityNoCity
country_codeNoCountry code (ISO-3166 Alpha-2 format)
email_addressNoEmail address
fax_numberNoFax number
is_activeNoActive status
labor_unionNoLabor union
license_numberNoLicense number
mobile_phoneNoMobile phone number
nameYesName
non_union_prevailing_wageNoNon union prevailing wage status
notesNoNotes (notes/keywords/tags)
origin_idNoOrigin ID
origin_dataNoOrigin Data
origin_codeNoOrigin Code
parent_idNoParent Vendor ID. Cannot be the same as ID. Only two levels of hierarchy are supported (parent/child).
prequalifiedNoPrequalified status
primary_contact_idNoPrimary Contact ID
state_codeNoState code (ISO-3166 Alpha-2 format)
trade_nameNoVendor's Trade Name, also known as Doing Business As (DBA).
union_memberNoUnion member status
websiteNoWebsite url
zipNoZip code
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create project vendor' implies a write operation but doesn't address permissions, side effects, or response format. The API path hint ('POST /rest/v1.0/projects/{project_id}/vendors') suggests it's a REST endpoint but doesn't explain behavioral traits like error handling or data validation.

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?

The description is extremely concise ('Create project vendor. [Core/Directory] POST /rest/v1.0/projects/{project_id}/vendors') but under-specified rather than efficiently informative. The API path adds some context but doesn't compensate for the lack of purpose clarity or usage guidance.

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?

For a complex creation tool with 29 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what a 'project vendor' is, the creation context, expected outcomes, or error conditions, leaving significant gaps for the agent.

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?

The schema description coverage is 100%, so the schema fully documents all 29 parameters. The description adds no parameter information beyond what's in the schema, meeting the baseline score of 3 for high schema coverage without additional value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create project vendor' is a tautology that restates the tool name without adding specificity. It lacks a clear verb-resource combination and doesn't distinguish this tool from sibling tools like 'create_company_vendor' or 'create_project_vendor_v1_1'.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or differences from similar tools like 'create_company_vendor', leaving the agent with no usage instructions.

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