Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update A Proposal Of The Project

update_a_proposal_of_the_project_company_v2_0

Update an existing Bid Board proposal's fields such as name, type, notes, scope, inclusions, exclusions, or primary estimate inclusion.

Instructions

Update a proposal of the project. Use this to update an existing Bid Board records (only the supplied fields are changed). Updates the specified Bid Board records and returns the modified object on success. Required parameters: proposal_id, company_id, bid_board_project_id. Procore API (v2.0): Preconstruction > Bid Board. Endpoint: PATCH /rest/v2.0/companies/{company_id}/estimating/bid_board_projects/{bid_board_project_id}/proposals/{proposal_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proposal_idYesURL path parameter — unique identifier of the proposal
company_idYesURL path parameter — unique company identifier associated with the Procore User Account.
bid_board_project_idYesURL path parameter — unique BidBoard project identifier
nameNoJSON request body field — the new name of the proposal, if the name should be updated.
typeNoJSON request body field — the new type of the proposal, if the type should be updated.
notesNoJSON request body field — the updated notes for the proposal, if the notes should be changed.
scope_of_workNoJSON request body field — the updated scope of work for the proposal, if it should be changed.
inclusionsNoJSON request body field — the updated list of inclusions for the proposal, if they should be changed.
exclusionsNoJSON request body field — the updated list of exclusions for the proposal, if they should be changed.
include_in_primary_estimateNoJSON request body field — indicates whether the proposal should be included in the primary estimate, if this flag should be updated.
Behavior3/5

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

Annotations already convey mutability and non-destructiveness. The description adds that only supplied fields are changed (PATCH behavior), which is a small addition. It does not disclose permissions, rate limits, or other behavioral traits.

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 four sentences, front-loaded with purpose, and includes necessary details like required parameters and API reference without unnecessary information.

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

Completeness4/5

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

The description covers purpose, required parameters, and endpoint. It lacks details on error handling or validation but is sufficient for a straightforward update tool with no output schema.

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?

Schema coverage is 100% with clear descriptions. The description highlights the three required parameters and explains that only supplied fields are changed, adding marginal value beyond the 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 verb ('Update') and resource ('a proposal of the project'), specifies it operates on Bid Board records, and distinguishes from sibling tools like v1 or create tools by mentioning the API version and endpoint.

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 says when to use it ('update an existing Bid Board records') and lists required parameters. However, it does not explicitly exclude alternatives (e.g., v1) or mention when not to use this tool.

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