Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Create BIM Mint Tokens

create_bim_mint_tokens

Creates a BIM mint token for a given project and returns it with a new ID. Use this to generate tokens for BIM preconstruction workflows.

Instructions

Create BIM mint tokens in a Project. Creates the BIM mint token 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. Procore API: Preconstruction > BIM. Endpoint: POST /rest/v1.0/bim_mint_tokens

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesJSON request body field — unique identifier for the project.

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

Adds concrete behavioral details beyond annotations: HTTP 201 return with a new id, non-idempotence ('calling it again creates another record'), and a failure payload with status codes (401/403/404). This aligns with annotations and provides valuable context without contradiction.

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?

Four concise sentences, each with unique value: purpose, success behavior, failure modes, and endpoint/required parameter. No redundancy or fluff, and the most important information is front-loaded.

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?

Given a simple one-parameter create with no output schema, the description is complete: it explains the return value (new id, HTTP 201), non-idempotence, and expected error statuses. No significant gaps remain.

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 schema has 100% coverage with a clear description for project_id ('unique identifier for the project'). The description only repeats that project_id is required, adding no extra semantics beyond what the schema already provides.

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?

Description gives a specific verb ('Create'), resource ('BIM mint tokens'), and scope ('in a Project'), clearly distinguishing it from sibling BIM create tools. It also adds non-idempotent behavior ('calling it again creates another record'), which further clarifies the tool's precise function.

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 for use: create the BIM mint token in a project, with project_id required. It does not explicitly mention when not to use or name alternatives, but the scope is unambiguous and the tool's purpose is well-defined.

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