Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project Naming Standard Rule

update_project_naming_standard_rule
Idempotent

Update an existing project naming standard rule to modify fields like name or definition, or set isActive to false to deactivate without deleting.

Instructions

Updates an existing project naming rule. Use isActive=false to deactivate without deleting. Send only the fields you intend to change; omitted fields keep their current values. company_id and project_id default to the values set by procore_set_config when omitted, and rule_id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified project naming standard rule on success. 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, project_id, rule_id. Procore API (v2.0): Core > Assets. Endpoint: PUT /rest/v2.0/companies/{company_id}/projects/{project_id}/assets/settings/naming_standard/{rule_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rule_idYesURL path parameter — unique identifier for the naming rule.
is_activeNoJSON request body field — whether the rule is active. Set to false to deactivate.
rule_nameNoJSON request body field — display name for the rule
rule_typeNoJSON request body field — optional metadata. NOT updatable: if provided, must match the existing rule's type; the server rejects mismatches.
company_idYesURL path parameter — unique identifier for the company.
definitionNoJSON request body field — rule definition. Shape must match the rule's stored type — for NAMING, supply expression_fields; for FIELD_DEFAULTS, supply actions. Sent as a raw JSON object; the server converts it to the correct...
project_idYesURL path parameter — unique identifier for the project.
descriptionNoJSON request body field — optional description
fieldset_idNoJSON request body field — new fieldset id. FIELD_DEFAULTS only; ignored / rejected for NAMING. Provided to recover a rule whose asset type's fieldset has been changed by an admin. Must match the asset type's current fieldse...
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?

Beyond annotations, the description discloses partial-update semantics (omitted fields keep values), config-based defaulting for company_id/project_id, return value, and error payload structure (401/403/404). This significantly extends the minimal annotation hints and does not contradict them.

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 dense but structured: it starts with the primary action, then key behaviors, return/error handling, and required params. Each sentence contributes information, though it is relatively long. It is appropriately 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 complex 10-parameter tool with no output schema, the description covers return value, error handling, partial update behavior, ID resolution, config defaults, and API endpoint. It is thorough enough for an agent to invoke the tool correctly with high confidence.

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 coverage is 100% and includes descriptions, so baseline is 3. The description adds value by explaining that company_id/project_id can be omitted (defaults from procore_set_config) and that rule_id must be resolved via a list tool. This goes beyond the schema's generic 'unique identifier' phrasing.

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 the verb 'Updates' and the specific resource 'existing project naming rule,' distinguishing it from create/delete counterparts in the sibling list. The mention of deactivation via isActive=false adds concrete scope.

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: existing rule updates, partial update behavior, resolution of rule_id via a list tool, and config defaults. It does not explicitly name create/delete as alternatives, but 'existing' implies non-creation. The guidance on deactivation without deletion adds specific usage context.

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