Skip to main content
Glama
TylerIlunga

Procore MCP Server

View Bid Form

view_bid_form_project
Read-onlyIdempotent

Retrieve a complete bid form's details by providing project, bid package, and bid form IDs. Get the full field set for a specific bid form in Procore, read-only.

Instructions

View single Bid Form. Use this when you already know which bid form you want and need its full field set. project_id defaults to the value set by procore_set_config when omitted, and bid_package_id, bid_form_id must identify existing parent records — resolve them with the matching list tool first. Returns a single JSON object describing the bid form. Read-only — it changes nothing in Procore. 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: project_id, bid_package_id, bid_form_id. Procore API: Preconstruction > Bid Management. Endpoint: GET /rest/v1.0/projects/{project_id}/bid_packages/{bid_package_id}/bid_forms/{bid_form_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
bid_form_idYesURL path parameter — unique identifier of the bid form
bid_package_idYesURL path parameter — unique identifier of the bid package
Behavior5/5

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

Beyond the readOnlyHint annotation, the description adds that it is read-only, returns a single JSON object, documents error payloads with common HTTP statuses (401/403/404), and explains the project_id default behavior, significantly enriching behavioral context.

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 a single dense paragraph with useful front-loaded information. It includes endpoint details and error handling without excessive verbosity, though it could be slightly more streamlined.

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 read operation with no output schema, the description covers return type, prerequisites, error conditions, default project_id behavior, and API endpoint, making it fully actionable for an agent.

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 descriptions already fully cover all three parameters (100% coverage). The description adds extra meaning by explaining the project_id default when omitted and requiring parent records to exist, but this is supplementary rather than essential due to high schema coverage.

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 'View single Bid Form', a specific verb and resource, and clarifies the use case 'when you already know which bid form you want and need its full field set', distinguishing it from list/index tools and company-level variants.

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

Usage Guidelines5/5

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

Explicitly states when to use ('Use this when you already know which bid form you want'), directs users to resolve IDs with the matching list tool first, and notes that project_id defaults to procore_set_config value, providing clear context for invocation.

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