Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Create A BIM Viewpoint

create_a_bim_viewpoint

Create a BIM viewpoint in a Procore project. Provide project_id and bim_viewpoint to receive the new viewpoint's ID.

Instructions

Creates a new BIM viewpoint in Procore. Creates the BIM viewpoint 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: project_id, bim_viewpoint. Procore API: Preconstruction > BIM. Endpoint: POST /rest/v1.0/bim_viewpoints

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesJSON request body field — unique identifier for the project.
bim_viewpointYesJSON request body field — the bim viewpoint for this BIM operation

Tool Definition Quality

A4.3/5.0
Behavior5/5

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

Adds valuable context beyond annotations: returns HTTP 201 with new id, non-idempotency, and common failure statuses (401, 403, 404) with error payload. This is exactly the kind of behavioral detail an agent needs. No contradiction with annotations.

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?

Concise and well-structured: purpose, behavior, error handling, required params, and API context in a few sentences. Front-loaded with the primary purpose. No redundant information.

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?

While the description covers purpose, errors, and endpoint, it does not explain what a BIM viewpoint is or what fields the bim_viewpoint object should contain. Since the schema defines it as a generic object with additionalProperties, this is a significant gap for correct invocation.

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% with both parameters described. The description lists required parameters but does not add meaning beyond the schema, especially for the bim_viewpoint object whose structure remains undefined. Baseline 3 is appropriate.

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 'Creates a new BIM viewpoint in Procore' with a specific verb and resource. It distinguishes from siblings like create_a_batch_of_bim_viewpoints (batch) and show_bim_viewpoint (read) by specifying this is a single record creation. The non-idempotent behavior is explicitly noted.

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?

Provides clear context that this tool creates a new BIM viewpoint and that calling it again creates another record, which guides when to use it. However, it does not explicitly mention alternatives or when not to use it, such as for batch creation via create_a_batch_of_bim_viewpoints.

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