Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A Bid Form

create_a_bid_form

Create a bid form for a bid package in Procore. Submit the required project, bid package, and title to generate a new bid form record.

Instructions

Create a Bid Form for a Bid Package. A bid form is needed to submit a bid, since the bid will be made against the bid form. Use this to create a new Bid Management records in Procore. Creates a new Bid Management records and returns the created object on success (HTTP 201). Required parameters: project_id, bid_package_id, title. Procore API (v1.1): Preconstruction > Bid Management. Endpoint: POST /rest/v1.1/projects/{project_id}/bid_packages/{bid_package_id}/bid_forms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
bid_package_idYesURL path parameter — unique identifier of the bid package
titleYesJSON request body field — bid Form Title
proposal_idNoJSON request body field — unique identifier of the proposal
lock_unit_fields_base_bidNoJSON request body field — lock unit fields for all base bid items. Must be sent explicitly (no inheritance from bid package). Defaults to false if not provided.
lock_quantity_fields_base_bidNoJSON request body field — lock quantity fields for all base bid items. Must be sent explicitly (no inheritance from bid package). Defaults to false if not provided.
lock_unit_fields_alternatesNoJSON request body field — lock unit fields for all alternate items. Must be sent explicitly (no inheritance from bid package). Defaults to false if not provided.
lock_quantity_fields_alternatesNoJSON request body field — lock quantity fields for all alternate items. Must be sent explicitly (no inheritance from bid package). Defaults to false if not provided.
base_bidNoJSON request body field — base Bids
alternatesNoJSON request body field — alternate bids
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the tool is a creation (non-readonly, non-destructive). The description adds that it returns HTTP 201 on success and creates 'Bid Management records', which aligns with annotations. It provides the endpoint URL and API version, offering useful behavioral context beyond 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, consisting of three sentences that cover purpose, required parameters, and endpoint. It is front-loaded with the main action. The inclusion of API version and endpoint is useful but could be slightly more streamlined.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 10 parameters (3 required) and no output schema, the description adequately covers the core purpose and required inputs. However, it lacks details about optional parameters and the structure of the returned object. The schema covers parameter descriptions, but the description could be more complete for an agent to understand all inputs.

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%, so baseline is 3. The description only mentions required parameters (project_id, bid_package_id, title) without adding meaning beyond the schema. It does not elaborate on optional parameters, but the schema itself is clear. Thus, no significant added value.

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 explicitly states 'Create a Bid Form for a Bid Package' and explains the purpose of a bid form, distinguishing it as a creation action. It's specific about the resource (bid form) and the action (create), making it clear what the tool does.

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

Usage Guidelines3/5

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

The description provides some guidance by listing required parameters (project_id, bid_package_id, title) and the success response, but does not explicitly state when to use this tool versus alternatives like 'index_bid_forms' or 'delete_bid_form'. No exclusions or when-not-to-use scenarios are mentioned.

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