Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show BIM Viewpoint

show_bim_viewpoint
Read-onlyIdempotent

Retrieve the full details of a specific BIM Viewpoint using its ID and project ID.

Instructions

Return a single BIM Viewpoint. Use this to fetch the full details of a specific BIM records by its identifier. Returns a JSON object describing the requested BIM records. Required parameters: id, project_id. Procore API: Preconstruction > BIM. Endpoint: GET /rest/v1.0/bim_viewpoints/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the BIM resource
project_idYesQuery string parameter — unique identifier for the project.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint as true, and destructiveHint as false. The description adds the endpoint and that it returns JSON, but no additional behavioral traits are disclosed. The description is consistent 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with the main action, and includes useful API context. Only minor waste like the typo 'records' instead of 'viewpoint'.

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?

With no output schema, the description only vaguely states it returns a JSON object. It could detail the response structure for better completeness, but given the parameters and annotations are clear, a 3 is reasonable.

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 input schema describes all parameters with 100% coverage. The description merely restates the required parameters without adding new meaning. Baseline 3 is correct.

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

Purpose4/5

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

The description clearly states it returns a single BIM Viewpoint by identifier, specifying the verb and resource. However, it does not differentiate from sibling tools like list or create BIM viewpoints, so a 4 is appropriate.

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 implies using this tool when you have a specific BIM viewpoint ID and need full details. However, it does not explicitly state when not to use it or mention alternatives such as list_bim_viewpoints for multiple records.

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