Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Quantity Log

update_quantity_log
Idempotent

Update an existing quantity log on a Procore project. Send only the fields that need to change; omitted fields stay as they are. Requires the project ID and the log ID.

Instructions

Update single Quantity Log. #### See - Daily Log guide - for additional info on * Attachments * Locations. Send only the fields you intend to change; omitted fields keep their current values. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified quantity log 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: project_id, id, quantity_log. Procore API: Project Management > Daily Log. Endpoint: PATCH /rest/v1.0/projects/{project_id}/quantity_logs/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Daily Log resource
project_idYesURL path parameter — unique identifier for the project.
attachmentsNoJSON request body field — quantity Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files.
quantity_logYesJSON request body field — the quantity log for this Daily Log operation
Behavior5/5

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

Beyond annotations, it discloses partial update semantics, defaulting of project_id, return value, and common HTTP error codes (401, 403, 404). This adds significant behavioral context not present in the annotations, and there is no contradiction with the 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 dense but well-structured, with each sentence providing useful information. It is longer than the ideal two-sentence example but not overly verbose given the complexity of the tool.

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

Completeness4/5

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

Covers purpose, partial update behavior, parameter defaults, error handling, and return value. The link to the Daily Log guide compensates for lack of detail on quantity_log's internal fields. No output schema, but the return value is described.

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% already, but the description adds meaning: project_id defaulting and the requirement that id must resolve from the list tool. This enhances understanding beyond the schema's field descriptions.

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 'Update single Quantity Log.' with the specific verb 'Update' and resource 'Quantity Log'. It is distinguished from sibling tools like create_quantity_log and delete_quantity_log, and the PATCH endpoint reinforces the partial update intent.

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 guidance on partial update behavior ('Send only the fields you intend to change'), how to default project_id, and how to obtain the id ('resolve it with the matching list tool first'). It does not explicitly name alternatives for create/delete but implies when this tool is appropriate.

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