Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Company Naming Standard Rule

create_company_naming_standard_rule

Creates a company naming standard rule by providing company ID, trigger field, and definition. Returns the new rule with its ID.

Instructions

Creates a NAMING rule for the company. Only one active naming rule per company is allowed. company_id defaults to the value set by procore_set_config when omitted. Creates the company naming standard rule 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: company_id, trigger_field, definition. Procore API (v2.0): Core > Assets. Endpoint: POST /rest/v2.0/companies/{company_id}/assets/settings/naming_standard

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rule_nameNoJSON request body field — display name for the rule. Optional: when omitted or blank, the backend auto-generates a scope-indicative name of the form '{rule_type}::{company_id}::{asset_type_id|NA}::{fieldset_id|NA}::{trigger...
rule_typeNoJSON request body field — rule type. Defaults to NAMING for backward compatibility.
company_idYesURL path parameter — unique identifier for the company.
definitionYesJSON request body field — structured rule definition. Shape depends on ruleType: FieldRuleDefinitionDTO for NAMING, FieldDefaultsDefinitionDTO for FIELD_DEFAULTS.
descriptionNoJSON request body field — optional description
fieldset_idNoJSON request body field — fieldset id (required for FIELD_DEFAULTS). '-1' for Procore default fields; external configurable fieldset id for custom fields. Null for NAMING.
asset_type_idNoJSON request body field — asset type id (required for FIELD_DEFAULTS; null for NAMING).
trigger_fieldYesJSON request body field — trigger field. For NAMING: asset_code. For FIELD_DEFAULTS: the field this rule configures (e.g., custom_field_1234, trade_id).
Accept-LanguageNoJSON request body field — locale for localized response messages (for example: en, fr-FR, pseudo)
Behavior5/5

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

Goes well beyond annotations by disclosing non-idempotency ('calling it again creates another record'), success response (HTTP 201), common error statuses (401/403/404), and the one-active-rule constraint. Annotations (idempotentHint: false, readOnlyHint: false) are consistent; no contradiction.

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 somewhat long but every sentence adds distinct value: purpose, constraint, default behavior, response, error handling, required params, and endpoint. It is front-loaded and not redundant.

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?

Despite lacking an output schema, the description covers return behavior (new id, HTTP 201), non-idempotency, error payloads, and the uniqueness constraint. For a create tool with 9 parameters and no output schema, this is thorough and complete.

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 description coverage is 100%, so parameters are already well-documented. The description adds extra meaning for company_id (defaults to procore_set_config value) and highlights required parameters, which is helpful 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?

Clearly states it 'Creates a NAMING rule for the company', naming the specific resource and scope. Distinguishes from siblings by mentioning company-level scope, 'Only one active naming rule per company', and the explicit 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?

Provides useful context: only one active rule per company, company_id defaults from procore_set_config, and lists required parameters. Does not explicitly say when to use this vs. update/delete variants, but the company vs. project scope is clear from the description and tool name.

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