Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Bulk Create/Update UI Flags

bulk_create_update_ui_flags
Idempotent

Create or update UI flags for a company and its users by providing the company ID and the fields to change.

Instructions

Create or update UI flags associated with company, and user. Use this to update an existing Company Settings (only the supplied fields are changed). Updates the specified Company Settings and returns the modified object on success. Required parameters: company_id. Procore API: Company Admin > Company Settings. Endpoint: PUT /rest/v1.0/companies/{company_id}/settings/my/avatar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.

Tool Definition Quality

C2.4/5.0
Behavior3/5

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

Annotations provide idempotentHint=true and readOnlyHint=false, which the description aligns with by stating it updates and returns the object. No contradiction but no added behavioral context beyond what annotations offer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Two sentences, but they contain conflicting information (UI flags vs. company settings/avatar). Concise but confusing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fails to explain the 'bulk' aspect, what UI flags are, or how to specify fields. The mismatch with the actual endpoint leaves significant gaps for 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?

Only one parameter (company_id) with full schema coverage. The description mentions it's required, which is already in the schema. No additional meaning provided.

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

Purpose2/5

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

The description states 'Create or update UI flags associated with company, and user' but the tool name and endpoint (PUT /companies/{company_id}/settings/my/avatar) indicate it updates company avatar settings. This mismatch makes the purpose unclear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus other bulk update tools. The description simply says 'Use this to update an existing Company Settings' without differentiation.

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